InstallAware

I have created an installation using the Quick Start wizard. I have written no scripts for this package, so it should be as close to default as possible. The only deviation I have made is to add our own top and side images to the dialogs.
The C# executable and library assemblies are added and the project builds perfectly.

As the assemblies rely upon .NET Framework 3.5, I added .NET Framework to the Application Runtimes.
Now, I get the following Script Load Error message:

This script uses a plug-in that is not available on your system:
{60DD7030-D10D-4765-8870-AA72BE159A0F}

Please install this plug-in before opening this script. Closing project now.

To install plug-ins:

1. Open the Control Panel "Add-Remove Programs" applet,
2. Choose the "Change" option for InstallAware,
3. Select "Add or Remove Features" and install missing plug-ins.

I have installed the july version of IA 9 R2. As this did not help, I tried the hotfix recommended by Michael Nesmith in a Technical Support forum article posted on May 25th. I even tried re-generating my license.

As long as I do not add any runtime requirements, the project builds fine. As soon as I check the Microsoft .NET Framework 3.5 with Service Pack 1, the build fails with the message above.

I installed the complete Studio version of IA 9 R2, and investigating the installed components as suggested above shows that all components actually are installed. When I point to the folder from which I installed IA, I am asked to indicate the location again, so repair fails. What is the correct location for repair? In the "Browse For Folder" dialog, I point to the folder to which I downloaded the IA installer. I never get past that point unless cancelling the repair. If the actual original setup sources location asked for in the "Add or Remvoe Features" wizard is the temporary folder used when unpacking the full installer executable, this should be properly noted in the "Add or Remove Features" wizard. I would appreciate if this folder be set by default to the value I guess is stored in Registry after a successful installation.

The version installed is 9.1.9010.2010
I also have installed the IA 9 Runtimes Update, version indicated in "Add or Remove Programs" is 1.1.

I have spent two days struggling with this problem now, and I would very much appreciate a hint or a solution.

Something sure sounds broken.

Try to use msiZap. You may be able to find it at:
C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0\\Bin

Or, search the web..

Instructions:
http://msdn.microsoft.com/en-us/library ... 85%29.aspx

Here is the IA product code:
{1AFF3E5C-E67C-4D36-8478-8C36491440C2}

After you zap InstallAware, try install once more and if you still have problems, we'll go from there.

Thank you for the hint!

I found that the older version (version 9) was still in the PATH environment variable, so there is a chance that upgrading did not completely remove the old version.

So I uninstalled IA, removed all registry keys containing InstallAWARE references.

I will try reinstalling tomorrow. Hopefully, I am able to build again then.

- MortSkil

I have now reinstalled IA R9. Still the same problem.

I tried to uncheck Microsoft XML Parser 6.0 only, and the installation project is possible to build.

Is the XML parser strictly needed? What can I do with it to overcome the problem?

This seems to be a problem similar to that in the topic http://www.installaware.com/forum/viewt ... XML+Parser.

What is strange, though, is that on my colleague's PC, the very same project builds fine. On our build server, though, the same problem exist. I did not zap InstallAware on the server, though. If you want to find out what the problem actually is, I wait for your advice before zapping on the server, in case there are some registry or other configuration/installation entries you would like me to ivestigate in order to get an exact explanation why I experience this problem.

If you copied the project from an existing one, try to cut and paste the code back into your script(s).

If that doesn't help, see if you can't find a difference between the machine the project builds on and the one it doesn't.

I have a very similar situation, giving me the exact error. I moved my development system from one computer (Vista) to another (Windows 7). I also made some changes in my project (not the script). I'm moving from .NET 2.0 to .NET 3.5

I get the same error if I select .NET 3.5. If I change the application runtime to .NET 2.0, it runs fine. I can select .NET 3.5 and deselect the Microsoft XML Parser 6.0, the build will start, but I get an error "Error during build: Failed to compile plug-in action: File Bag"

Does a "File Bag" folder appear in:

<install path>\InstallAware\InstallAware 9 R2\Plug-Ins

Yes, that folder appears. It has "mFileBagEXE.dll" and "mFileBagIDE.dll".

Some thoughts. My original development system has the program installed, and I recall that we might have had to do some ADDITIONAL installation of the files for .NET 3.5? I don't recall the details of installing the program there, and for some reason I'm not capable of doing a search of this forum that works (I always get a totally blank page when trying to search the forum). My fuzzy memory, there were some additional installs. Your "download" page on the support site is empty when I look there.

My new development system was set up recently, and I used the install file you provided to me originally. I probably didn't do any additional installation steps, if any were required, to get .NET 3.5. Again, I'm very fuzzy on this issue and can't find notes about it on your web site.

I moved the install project files from the old system to the new system. The old install project was using .NET 2. On my new system I wanted to work with .NET 3.5. So I edited the project to change the paths of files and change it to use .NET 3.5. This fails.

Drop .NET 3.5 on the new system, it builds (but without .NET files that I want).

Change it to .NET 2.0, it builds fine.

THEN, I went back to the old system. Changed it to use .NET 3.5, And it works. However, I don't want to use the old system for a number of reasons. It is creaky and needs to be retired.

So there is something wrong or missing on my new system. Again, my fuzzy memory was that I had to do something to set up .NET 3.5 on my system, I just don't recall the details.

Can you try to create a new project (use basic template) and add .NET 3.5 to see if that throws an error?

What version of InstallAware are you using?

I created a brand new project using the .NET template. Set it to use .NET 3.5. Added a single "file". Clicked the "single file" build icon. Immediately got the same error message.

Note that when I close that error dialog I get a second error dialog "Unable to find saved script context for", with nothing after the "for".

InstallAware 9 (Build sliders.rtm.042009)

When you check off .Net 3.5 in the Runtimes view, does it include other runtimes as well or does only 3.5 check off?

Do (check/setup) scripts for the .Net 3.5 get added to your project after including it?

Yes, if I check .NET 3.5, it also checks 3.0, 3.0 Service Pack 1, and 2.0 with Service Pack 1
I can send you files if you wish...

Regarding your question

Do (check/setup) scripts for the .Net 3.5 get added to your project after including it?

- I don't know how to answer that. I am not a sophisticated user of your product, I pretty much stick with the design view and check of boxes...

I am confused about one thing - if I include .NET Framework 3.5, why do we have to include the lower levels? When I went from .NET 2.0 to .NET 3.5 (on the older machine that seems to work with this) my installer file tripled in size...

I was able to isolate the problem to setupmsxml60.mia (added when you select the runtime Microsoft XML parser 6.0, which is a pre-requisite for .Net 3.5).

You should be able to get by with unchecking the Microsoft XML parser 6.0 runtime, but if you want to include it, you can place the attached version in:

<install path>\InstallAware\InstallAware 9 R2\runtimes

You may need to uncheck and recheck the runtimes in your project and/or delete setupmsxml60.mia from your project folder.

Also, IA 10 does not exhibit this issue.