InstallAware

Hi,

We're using 5.31 (we haven't had the chance to upgrade to the new version). We're having a problem with the .NET web media block that I've been trying to resolve.

When we run the installer on a system (XP home for example) that doesn't have .NET I eventually get:



This happens after the progress bar has gone by a couple times which leads me to believe it downloaded the .net web media block ok but failed to run/execute it. I've tried a couple of different servers and verified that the web media block is accessible.

Now, the interesting part. After this failure, it continues to install our product. If I rebuild the installer and run it again it notices it is an upgrade, that .NET is missing, and tries to install it. And, it succeeds! I don't get the error.

I've tried rewriitting the web media block again and agian, re-entering the .NET framework plug-in line a few times to no avail.

I've also tried building the installer on another machine with the same results.

I've also tried making a new sample .NET install and running that. That works fine. I've taken the script code from the sample and tried to use it in our installer but that doesn't work either.

Is there any way to get more information out of the installer as to what is going on? Is there debugging/logging that we can use with the .NET install to help? If not, can we possibily get a special version of the plug-in with debugging?

What are the dependencies for the .net plug-in to work? Could there be something that is missing when the plug-in is run?

Of interest since my post:

We found the installer files on the system where the install was failing. There was a "Microsoft .NET Framework 1.1" directory. In it was the .net installer (from Microsoft) and running it manually installed .NET fine.


Also, I tried downloading an eval of 6.05 and using it and it works too. Of course, this is the day before we're trying to release a new build so we're a little uneasy introducing anything majorly new.

Actually, I think the safest way would be for you to go with version 6 at this point. There were some issues in 5.x which might have been responsible for this problem, it would be very error prone and unreliable (if at all possible) to attempt to resolve them at the eleventh hour.