standalone builds do not install .NET 2.0 assemblies

[Clairealex77]

My setup contains 3 .NET 2.0 assemblies that use installutillib.dll to run custom actions.
When I build with the IDE or with IsCmdBld.exe, the setup produced installs fine.
When I build with the standalone (IsSaBld.exe), the setup fails with installutillib.dll errors.
The behavior is exactly the one described in Q111934, but the hotfix does not solve the problem for the standalone tool.

Is there any hotfix in preparation for the standalone tool to address this issue?

This is critical for our company, as we want to ship our product this month...

[Greg Smith]

I'm having the same issue with the standalone build tool. When I use the UI through Visual Studio 2005, the solution builds and the installer installs Framework 2.0 assemblies successfully (including install util'ing using the InstallUtilLib functionality). The standalone build tool reports success on compilation, but the resulting installer fails with an error "Error 1001.InstallUtilLib.dll: Unknown Error.".

Using ORCA I can see that there is a difference in the custom action table for the install util actions. The standalone build tool is NOT appending the "[SUPPORTDIR]\_isconfig.xml" text to the end of the target cell. The verbose install logging also shows this parameter as missing when calling the InstallUtilLib.dll. When I switch back to Framework 1.1 (using the -t switch) this parameter is appended but the InstallUtilLib fails because the format of the assemblies (2.0) is unknown.

As my company uses an automated nightly build process, this issue is a showstopper. I've only just identified the issue when upgrading our product to Framework 2.0 and InstallShield 11.5 (everything worked well with Framework 1.1 and IS X).

Any ideas?

[Clairealex77]

Did you try editing the custom action table in the msi?
I will do it and see if it is solving the problem.

[Clairealex77]

I was able to implement a work around. I use WiRunSQL.vbs, a script provided in Microsoft SDK, to edit the custom actions created to install the .NET assemblies, appending "[SUPPORTDIR]\_isconfig.xml" to the Target field, in the msi built by IsSaBld.exe.

[SherylSikora]

We are currently working on a fix to the InstallUtilLib.dll errors for the StandAlone Build. I apologize for the inconvenience and I will keep you posted on the availability of the StandAlone version of this fix.