This content has been marked as final. Show 4 replies
You could do that provided you pointed each layout to a different target but it seems to miss the point of merged help. The idea is you generate it all once and then deliver just what is wanted. If a particular set up does not require Child 2, simply don't deliver it and the merge still works.
Sorry for missing the simple thing...am not sure how the above can be acheived?
What am doing is merging all 3 helps in one project(parent), and have a SSL which generates this 3 projects. Is there a way that we can set not to publish one of the merged child projects?
What I am doing is simply generating different outputs before merging projects, e.g. Project A and B - create output, then remove Project B and merge Project C and generate project A and C. I know kinda silly but thats the only way I was able to do it.
Generate the whole lot and then create a couple of copies of the output.
In one copy, go to mergedProjects and delete any child project. Open the startpage of the parent and you will find you have a merge but without that child.
Now go to the other copy and delete a different child. Open the startpage of the parent and you will find you have a merge but without the child deleted in this copy.
The merge occurs when the startpage is opened by the user. It presents whatever children are found. If any are not there, they will not appear in the TOC, index or search.
Experiment a bit with copies and you'll soon see how it works.
Does that clarify it?
Yes that helps alot..now it makes sense..hehe..
Will give it a try and let you know.