Hi Robbe,
Thanks for posting this, this is the only resource that I have found for launching another MSI from set up and deploy. I have found the standard tools very restrictive and its good to know that you can add some customallity through scripts.
However I'm quite new to programing and having some problems getting this to work.
All I want to do is launch a second MSI that is allready made at the end of the one that I am creating. I have copied your first class from the example, and am trying to get it to build, I have changed the following code...
path = GetParameter( "assemblypath");
path = path.Replace( @"\class1.dll", "");
appName = Path.Combine(path, "PBCLTRT110.msi");
class1 is the class libary that I added to the solution, and PBCLTRT110.msi is the MSI I am trying to launch.
I am gettin the following errors;
Error 1 Static member 'System.Diagnostics.Process.Start(string, string)' cannot be accessed with an instance reference; qualify it with a type name instead C:\Documents and Settings\alexis.coles\My Documents\Visual Studio 2005\Projects\Alfi Setup\RunMSI\Class1.cs 135 21 RunMSI
RunMSI being the namespace I have to class1 and
Error 2 Unspecified module entry point for custom action 'C:\Documents and Settings\alexis.coles\My Documents\Visual Studio 2005\Projects\Alfi Setup\RunMSI\obj\Debug\RunMSI.dll'. C:\Documents and Settings\alexis.coles\My Documents\Visual Studio 2005\Projects\Alfi Setup\Alfi Setup\Alfi Setup.vdproj Alfi Setup
I guess the second one is something to do with the /autostart=[AUTOSTART] Line of code that I have left commented out as I do not really understand what to do with it.
Would be very greatfull if you could explaine these parts in a little more detail.
Many thanks |