I had similar issues using the Crystal merge modules. This problem is because the dependencies the Crystal runtime DLLs have on the Microsoft MFC framework for the targeted version of Visual Studio. You need to make sure that the needed runtime is installed ahead of time, so that when the Crystal DLLS are registered the dependencies can be found.
Unfortunately, including the Microsoft runtime merge modules does not work in this case. The Microsoft MFC runtimes must be installed ahead of time for everything to function. Mat Skildum -----Original Message----- From: Jagdish S. Khedekar [mailto:jagdish.khede...@kpitcummins.com] Sent: Thursday, September 15, 2011 4:50 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problem incorporating merge modules for Crystal Reports for VS2010 Hi All, I need to incorporate merge modules for "Crystal Reports For Visual Studio 2010" into my existing WiX project. I have already followed the standard steps for adding 'Merge Id' and 'MergeRef' elements and initially it seems working properly. But while using my installed application, I get various errors related to Crystal Report which are being caused by not finding proper dlls, or some registration issues. I tried to google on related information, where most of the recommendation says not to use merge modules. I also tried to modify the 'InstallExecuteSequence' and to have some 'EnsureTable Id' elements, but couldn't help much with it. Please let me know if anybody on the list have faced similar issue and could get resolution on it. Also please let me know if there are any alternatives to resolve this issue. Note: There are some warning I am getting while building my WiX project as below - warning LGHT1056 : The Directory table contains a row with primary key(s) 'DesktopFolder' which cannot be merged from the merge module 'C:\CRforVS_MergeModules_13_0_1\CRRuntime_13_0_1.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module. warning LGHT1055 : The InstallExecuteSequence table contains an action 'SetIISNET2VIEWERDIR' which cannot be merged from the merge module 'C:\\CRforVS_MergeModules_13_0_1\CRRuntime_13_0_1_es.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module. Thanks and best regards, Jagdish. ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
