InstallAware

ohali wrote:...unless sharing an assembly is explicitly required."

That's exactly what the GAC is designed to achieve.

I'm surprised MS have seen fit to issue a waiver. They are almost implying you can park your car anywhere where you want but don't look to us if you get a parking ticket.

I am having this problem with an install project that worked OK 2 weeks ago.
The IA version that I am using is: 10(Build Mooya.rtm.51110)
I am running on WIndows 7, 64-bit.
The .Net assemblies that I have generated are targeted specificaally to then X86 platform.

The responder in this thread earlier asked what assemblies are failing. Here are a couple of examples in my project

Microsoft SQL Components in Prog Files (x86)\MS SQL Server\100\SDK\Assemblies
Microsoft.SqlServer.ConnectionInfo.dll
Microsoft.SqlServer.Sml.dll
(there are 8 of these that I currently use)

GrapeCyty licensed components in Prog Files (x86)\ActiveReports 6 Activereports.XlsExport.dll
ActiveReports.Chart.dll
There are 8 of these that I am currently using)

FYI: GrapeCity uses InstallAware to build its product release installation programs

All of my application specific assemblies also fail with the same error condition.

Have you tried to install these assemblies into the GAC?

These are from Micrisoft and other 3rd party licensees. Souldn't they remain where thoe companies have targeted them for the developer.

Also, my project built OK 2 weeks ago. In the interim I have installed an to IA 10 update based on the automatic notification from IA.

Norm

Well, it does not do any harm if you install the first of the assemblies in question in the GAC and see what happens. If there is no improvement you can easily uninstall the assembly from the GAC and the original installation remains untouched. Just try it out.
If I were you, I would not wait for a solution from IA, because this is no new topic and there is still no solution available after all these month.

The GrapeCity assemblies are in the GAC and under the Program FIles (x86)\Common Files folder structure.

However, IA will not alloww me to select a file that is in the GAC on my development machine to add it to the project using the Add "Open File" dialog.

If I edit an existing Assembly in my project and override its path location to point to he GAC, it still does not show any of its information (Name, Version, Culture, Public Key)

Thanks,
Norm

Thanks Ohali,
I did submitt a support request to IA, just after posting my question to the forum.

The threads that I have seen on this date back over a year. Does this problem come and go between updates to the IA product?

For anyone's interest in reviewing this thread.
The functionality to retrieve .Net Assembly information for a build script is BROKEN IN IA VERSION 10.10

After having this problem with version 10.1 and not getting any helpful reply, I uninstalled version 10.10 and reinstalled version 10.00 and the problem went away.

Dear Norman,

I am looking into this right now and I am able to build my IA 10.10 project when I add the assemblies you mentioned earlier as an example. Could you send your 3rd party assemblies to me so that I can try to install them in IA?

I have tried to upload the zip of those licensed files twice. The progress bar reached 100% each time and then I get rerirected to a "page not found in IE".

Did you receive the files or should I keep trying?

Norm

Hi,

The attached zip file contains the full path to the assemblies as installed. I have only included a couple of them. Please make sure that they are not accessible for download from your forums or knowledge base since they are licensed modules. (My first upload ended with an IE error)

FYI: I uninstalled IA version 10.10 and reinstalled version 10.00 and the "Unable to get assembly information" message has gone away. I am getting "bad assembly image statements for my application specific assemblies which I will sort ot on my own for now.

Thanks,
Norm

Dear Norman,

I have tested your assemblies on a clean Windows 7 with InstallAware 10.10 and experienced no such problems.
Its interesting because a different user is reporting y the same problems you are experiencing; I suspect that it had to do with your InstallAware installation and by removing it and installing a different one you solved your problem...

I will reinstall 10.10 this evening and try it again.
Will update this thread with the results.

Hi Aviv,

It is more prudent for me to wait until I finish my current build cycle before trying to reinstall version 10.10 so it will be a couple of days before I can get back to you on this.

Norm

No problem Norman. I appreciate your patience!