drspringthumb
26th April 2006 16:21 UTC

NSIS installer conflicts with .NET 2.0 installer
We're using an NSIS installer to install the .NET Framework 2.0, among other things. The .NET installer sometimes stops during its installation to complain that the NSIS installer needs to be shut down before it can proceed. We can't seem to intentionally reproduce this, but it's happened often enough to be alarming.

We can tell the .NET installer to "Ignore" the problem, and that seems to satisfy it. But it would be unprofessional to force our users to do that. Any thoughts?

Takhir
26th April 2006 17:50 UTC

The only idea I have is kichik' .net version check out example using System plug-in, dll to be replaced may stay locked if installer (or OS) not unloaded it yet.

drspringthumb
26th April 2006 20:04 UTC

I'm not sure what you mean--could you point me to the example?

kichik
28th April 2006 12:14 UTC

If you're using GetDotNETVersion, which uses mscoree.dll to check for .NET, your installer has mscoree.dll loaded while the other installer wants to update it. You can use the 'u' flag to have the System plug-in unload mscoree.dll after it's done with it.

System::Call "mscoree::GetCORVersion(w .r0, i ${NSIS_MAX_STRLEN}, *i) i .r1 ?u"