3 replies to this topic

[RikRak]

Hi all,

I'm new to InstallShield so forgive me if this is a stupid question...

I'm using Installshield 12 to install a .NET 2.0 application. I had been using VS2005 setup project which included a number of Custom Actions, but have decided to use a more advanced installation editor.

I'm wondering whether to continue using Custom Actions with Installshield, or whether to just use InstallScript.

Is there a general consensus as to whether Custom Actions are better than using Installscript or vice-versa?

Any thoughts welcome.

Rik

For info: the Custom Actions setup the .NET CAS policy, made changes to the configuration file, and setup the registry.

[Stefan Krueger]

Using custom actions is better in a Basic MSI project is better than using the InstallScript MSI project type.
You can have custom actions in a couple of formats, including DLL, EXE, VBScript, InstallScript, .NEt Installer Class. A DLL written in C is often the leanest and most stable solution. Custom Actions written in InstallScript require some overhead. Custom actions in managed code (c# for instance) should be avoided.

[RikRak]

Thanks Stefan,

Is there any reason why managed custom action should be avoided? Is it because the framework is required prior to installation?

Rik

[Stefan Krueger]

See this blog article for some discussion:
http://blogs.msdn.co.../10/392280.aspx
Also note that you are very restricted in scheduling "installer class" custom actions.