Unable to get assembly information

[giaviv]

Dear Norman,

Have you not received my emails regarding this?
Since this issue is specific to you, lets work it out privately and post the solution once we get to it here.
I am emailing you again now.

[Christian.Holm]

I am afraid I am seeing same problem.

After upgrading from 10.0 to 10.10 a couple of days ago - I get the problems that the build installer insists on running RegAsm.exe from .net 4.0 directory even if it does not exist - that is .NET4 is not installed.

"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe" this is the file which the installer "wants" to use even if it is not there...

Any help would be appreciated - right I'll try and downgrade my InstallAware

Regards
Christian

[NormanDerrick]

Hi Aviv,

The problem with my normal business phone line has been resolved.
If you can give me a call at 310-791-5615 so that we can work through a resolution and then post it online, that would be good.

Norm

[NormanDerrick]

Hi Aviv,

I tested the simple script with a single assembly that you sent back - building it on my workstation AFTER installing SP 1 for WIndows 7 and it still fails. Just to verify that it is not a Windows 7 specific issue, I also ran the install script on an XP test machine and it fails there also.

I have not gotten around to installing InstallAware on a different box as a test yet.

Norm

[giaviv]

Dear Norm,

Thank you for your update. We are looking at this problem, it seems to be quite wide spread.
Please keep me in the loop about your tests and so will I.

[giaviv]

Dear InstallAware users,

We apologIze for this issue. The message box has been removed (just regenerate and reinstall your license now to get the fix).
In order to help us solve the problem, please run regasm from the command line with the same parameters as are displayed in the error BEFORE installing your fixed license and attach a screenshot of the regasm output. Furthermore, do the assemblies install successfully despite the error box? Do they after the fix?
Thank you for your patience!

[alibaba]

After upgrading to Windows 7 and a new installation of IA10.10 the problem I reported in this thread dissapeared.

[giaviv]

Great!

[Obliterator]

I'm encountering the "unable to get assembly information" on one of my assemblies.

Whats strange is IA used to build my project without problem!
I have eventually worked out the cause, by rolling back through our source control and inspecting the differences closely.
Althrough I've found the cause, I can't find a proper solution.
I'm posting here as it may help get the matter resolved or at least help others who encounter the problem.

The problem has arisen since I changed my assembly to target .NET 4.0 in the project settings.
Previously my assembly was built to target .NET 4.0 Client Profile.

If my assembly is built targetting .NET4 Client Profile then IA works perfectly.
Change the build to target the full .NET4 framework and IA fails to get the assembly information.
I have no idea why the target should break my IA build in this manner.

I've worked around the problem by switching back to target .NET4 Client Profile.
Hopefully IA can look at this in more detail. I should add I'm currently still using IA 9 SP3.

Let me know if you would like me to send you the two builds of my assembly.

[giaviv]

Are you installing the assemblies to the GAC?

[Obliterator]

Not the one that's failing no, just to my target dir.
FYI: It's not digitally signed or strong named either.

My setup is installing some other third party shared assemblies to the GAC, but IA is working for these. Only my assembly to target dir fails and then only if its built in VS targetting full .net 4 rather than client profile.

[NormanDerrick]

Hi Obliterator,
I continued to use IA 9 SP3 because of the error getting assembly information until version 11 came out. With IA 11, the problem that I experienced with IA 10 and IA 10.1 getting assembly information went away (with the workaround mentioned below). As a technician, I don't understand what caused the issue but I am pleased that it is no longer present.

One thing that I had to do and left in "because it is working" was to create my own command files to perform the gacutil step for the install / uninstall on the client. These are run are part of the script once IA has done its thing. At some point when there is time, I will try to let IA do this for me to see if it will work again.

I recently downloaded IA 12 but have not installed it yet for testing.

Norm

[Obliterator]

Thanks for the feedback. Hopefully IA can get to the root of the problem (if they haven't already in later versions).
For me the problem is not (presently) so urgent as I can live with my assemblies using Client Profile for now.

I'm also planning to evaluate IA12 myself this week so I'll test how that behaves too.

[Obliterator]

Did IA support ever get to the bottom of this issue?

I'm still using IA 9R2 SP3 but one of my setups suddenly no longer builds.
IA complains with the "Error during build: Unable to get assembly information for xxxx.dll".

I'm not installing to the GAC and I've even tried adding a strong name key. Still fails.
Its really strange as my project settings haven't really changed - so I can't understand the sudden failure.
My assembly is a .NET 4 Client Profile assembly which used to work fine in IA (previously only had problems with full .NET 4 assemblies).

What are the command line options for mGacInfoX.exe so I can try to see what exception is being thrown.
How can I better diagnose why it fails to get the assembly info?

Any help much appreciated.

[FrancescoT]

Dear User,

let me to check about and I will be back to you.

Just a question, have you tryed with IA 2012?

Regards