Page 1 of 1

InstallAware Unable to Get 64-bit Assembly Info

Posted: Thu Jul 16, 2009 5:22 pm
by Bennett G
I have an InstallAware 7 project that we used to successfully create an installation package for our 32-bit software application. We have recently ported our app to Windows x64 and I am working to update our InstallAware project to support our new 64-bit code.

I am using the same core project that we successfully used for our 32-bit installer, and I'm running InstallAware on an x86 computer. When I attempt to build, I receive the following error:

Error During Build: Unable to get assembly information for [file]

The [file] is our 64-bit .NET Assembly. Note that this same project works fine when [file] points to our 32-bit .NET Assembly. Both the 64-bit and 32-bit .NET Assemblies are compiled from the same code using the same copy of Visual Studio 2008.

What is InstallAware looking for in the 64-bit Assembly that it can't find?

Thanks,

Bennett G

Posted: Thu Jul 16, 2009 6:01 pm
by MichaelNesmith
I believe it might have worked running on an x64 system - are you able to test this scenario?

Posted: Thu Jul 16, 2009 9:37 pm
by Bennett G
Hi Michael.

Yes, you are correct. I setup InstallAware on an x64 system and successfully built my 64-bit InstallAware Project without receiving the error. Thank you for your quick and helpful suggestion.

However, my license for InstallAware is on my x86 dev machine. It looks like I'm going to need to build my 64-bit installation packages from my x64 dev machine. Is there a workaround to allow me to build 32-bit and 64-bit installs from my x86 machine?

Thanks,

Bennett G

Posted: Fri Jul 17, 2009 12:42 pm
by MichaelNesmith
You can transfer your license(s) as easily as uninstalling from the old machine(s) and installing to the new machine(s).

If your edition is Studio or higher, you don't even need a license for additional build machine(s) - as long as you don't fire up the IDE, you'll be fine.

You can even "float" your IDE if you have a floating license add-on.

I'm afraid no other solutions are available at this time :(