backpacker299
10th July 2007 15:54 UTC

Files Fail After Packaging
I am developing an installer for a .NET 2.0 application and I am having a very peculiar problem. I can run the application using the same set of files I later package into the installer and the application runs fine. After I package it into the installer and install it on a machine I get mysterious problems, including an unloadable DLL error (for a DLL that is up to date and is in the install directory). Is there anything that anyone can think of that might be causing this? Am I even right to think that the problem could be coming from NSIS?

Thanks,
Nik

Red Wine
10th July 2007 16:44 UTC

Does this happen on a different machine or on the same where you can run your app before packaging?

Is the $INSTDIR created correctly and all files copied intact?

Did you try to turn off the compression?

backpacker299
10th July 2007 16:53 UTC

It happens on the machine I build it on and on a different machine.

All files seem to be copied intact and correctly.

I didn't know I could turn off compression.

Red Wine
10th July 2007 17:14 UTC

I suppose the problem persists even if you attempt to run the installed application by clicking on the executable instead of clicking on the created shortcuts.

If it isn't big trouble give it a try without compression, use SetCompress off on top of your script.

kichik
13th July 2007 10:10 UTC

I'd guess it's related to the registration of the files. If you're packaging .NET assemblies, you need to register them using gacutil or another method.