Hi, I would like to know how to add a dotnet framework 2.0 merge module to a msi that I have created. I know in AdminStudio direct edit mode there is a Redistributables section under Application Data but I don't see dotnet in there and I don't know how to get it in there. Once the msm has been added how does the MSI know to install it? Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If you are using AdminStudio, you can goto "Redistributables" section and right click and choose "Browse to Merge Module". After this you shoudl be able to see your MM in the list.
Another way to cross check is goto DirectEditor and check for COMPONENT or FILE tables and find out the merge modules entries. Name of the component or file will come with a guid such as "CompoentName.1233423...".

Once you include your merge module into your MSI, every thing from your MM gets merged into MSI Database tables and installation of MSI does everything. MMs are just redistributable which can be used with MSIs.
Answered 10/09/2008 by: zipsantro
Purple Belt

Please log in to comment
0
After this you shoudl be able to see your MM in the list. the OP already said that the MM isn't in his list. However, I presume IS is like Wise, in that you can browse to other folders?

Having said that, I did some research and found this MSDN article, Using Visual Studio .NET to Redistribute the .NET Framework http://msdn.microsoft.com/en-us/library/ms994427.aspx

Caution Deployment projects for applications that reference the .NET Framework automatically add a merge module (dotnetfxredist_x86_xxx.msm, where xxx represents the language code) in the detected dependencies folder. This merge module cannot be redistributed; it exists for internal use by the project to prevent individual .NET assemblies from being listed. It is excluded by default; attempting to include it will cause a build error.
Answered 10/10/2008 by: VBScab
Red Belt

Please log in to comment
0
Instead of adding the dotnet framework merge module; every client should have the .NET Framework as part of their standard client as it's a "system component". So distribution it as a separate package or use a bootstrap (wrapper) to handle the framework installation.
Answered 10/10/2008 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity