Hi,
I want to distribute my software as a merge module so that partners and other developers that rely on it can distribute it in their setups.
It turns out that there are a lot of restrictions in merge modules:
- I can not reference another merge module
- I can not create features
The reason I wanted to use features is because I am deploying 2 versions of my software: one for .Net 1.1 and another for .Net 2.0. They both need to be installed, but only 1 of those will be active (i.e. will have the shortcuts pointing to it, will have a service set up etc..) I do not want to split this up into 2 separate installs, because most users don't know which version of .Net they have on their machine, and I want to make it as easy as possible for them and let my setup make the choice. (they are not compatible so the 1.1 assemblies do not run on the 2.0 CLR and vice-versa)
In order to detect which version of .Net will be active, I will have to put a condition on almost all of the components. I do not want to specify this condition (which could be fairly complex) manually on each and every component. That's why I wanted to organise them into a .Net 1.1 feature and a .Net 2.0 feature. Then I would only have to apply the condition on those 2 features and that would be done.
Since creating features is apparently not supported in a merge module, I tried to move all the files into the same component using drag and drop (is there an easier way to do this, because there are hundreds of files and this is very time-consuming?).
This appeared to work at first, but the I started to get this error when trying to add files from a different target folder: "The file you are trying to move should be key member in its component and in the new component it will not be key member! Are you sure you want to move it?"
What does that mean? Is this going to cause problems if I answer "yes"?
Is this the best approach for what I am trying to do, or will I run into further problems if I continue with the merge module?
Would it be better if I created this as a professional or enterprise project? If I do that though, will my partners still be able to distribute my software setup in their own setup?
Thanks
Mat
FOLLOW US
Get the latest news in Application Packaging