Hi,
At last we figured out the issue. The issue is when you want to run .NET based custom actions, Windows installer is not able to identify the exact .NET version (CLR version) and load the appropriate InstallLib and excute the .NET based custom action dll. This could be resolved in the following way
CPP Application have a method which takes MSIHandle as parameter
-Use CLR Hosting to hoat a specific version of .NET (C++)
CorBindToRuntimeEx
-Load the assembly from within this hosted CLR using DefaultApplicationDomain or created new application domain
ExecuteInDefaultDomain
Build with .NET support (/clr )
make the .NET method static
Now you can have CallDLLFromInstallation - with MSIHandle as parameter
-Other option is - Dont depend on .NET;-) Write CPP code to do full operation.
Main Topics
Browse All Topics





by: Abh4ITPosted on 2008-09-07 at 20:14:14ID: 22414459
Hi, I guess I assumed .NET means Windows and The question is using Wise Installer Studio 7.0 together with VS.NET. The question should be relevant for all working on the deployment aspect using Windows Installer