Unable to get assembly information

[NormanDerrick]

Hello Aviv,

I have uninstalled and re-installed version 10.10 as you suggested and the problem still exixts.

Thank You,
Norm

[giaviv]

Dear Norm,

We recently learned that this problem has to do with incompatible license and InstallAware version.
Please regenerate your license from your InstallAware account and make sure that your license is compatible with the version you are running.

[NormanDerrick]

Thanks Aviv,

That appears to have resolved the problem with retrieving the assembly information.

I re-built my project with build 10.10 (no changes from when it was built with 10.00) and when I installed it to my test machine I get error dialog for regasm.exe on all of the assemblies that are specific to my application. Each of these error messages showed double backslashes in the file path. Here is an example:
C:\Windows\Microsoft.Net\Framework\4.0.30319\regasm.exe /tlb "C:\Program Files\\FSO6.Messages.dll".

These did not occur with the install script generated by build 10.00
Does this ring a bell with issues reported by others for build 10.10?

The application ran OK for my initial testing though.

Thanks,
Norm Derrick

[alibaba]

I have the same problem...But the double backslashes are not the problem because I also get the error if I remove the double backslashes. So what to do now, how can I register assemblies. It worked with IA9 and IA10.0...

[giaviv]

Guys,

I am actually able to register assemblies with IA 10.10. Could you please make sure that your license is regenerated and installed and send me an assembly that doesn't register for you (and a description of how you register it)?
I am sorry about your issues - lets try and resolve them.

[alibaba]

Thank you for your help. I already sent you an email.

[NormanDerrick]

Hi Aviv,

Yes, I did re-generate the license and installed it (I assume that the get assembly information would still not be working if I had not but that is now working).

The attached zip file contains one of the tiny assemblies that do not register. Note that this problem is only occurring with the Assemblies that are specific to my application. Thy are developed on Windows 7, X-64 but compiled specifically for X86.

I forgot to answer your question on how I am registering them:
Using the IA IDE, they are included in the list of Assemblies
The target install folder is $TARGETDIR$
The Additional Options of "Generate Native Images" and "Register Assembly" are both checked.

Thanks,
Norm

[giaviv]

Dear Norm,

I truly apologize for these issues. Here are the steps that I took to register your assemblies:
1) Created a project from the Basic Setup template
2) Added your attached dll as an assembly in the design view
3) Changed the target of the installation of the assembly to $TARGETDIR$
4) Checked Register Assembly and Generate Native Images
5) Compiled and ran my project - it worked perfectly and succeeded with the assembly registration
I am running 10.10 on a Windows 7 x64. In light of this, are you sure that you properly reinstalled and regenerated your license?

[NormanDerrick]

Hi Aviv,

I am a little confused with our closing question.
There is not much that I can control about the installation to make it "improper". I selected the Studio Product, selected Complete Install, and left the default "for All Users".

There is no way that I can see to "improperly" run the license registration. I accepted the License and clicked the next button through the wizard.

Is there some "hidden trick" that I am missing?

Norm

[giaviv]

Dear Norm,

I am sorry, I didn't explain myself properly. I meant:
a) are you sure that the license was indeed regenerated and installed on the machine and
b) are you sure you have a valid 10.10 license?
The steps you are describing sound correct. I would uninstall IA all together, go to www.installaware.com/myinstallaware and click on regenerate license. Then, download that license, reinstall IA and install the license.

[NormanDerrick]

Hi Aviv,

I regenerated and downloaded the registration key program; uninstalled IA 10.01, reinstalled IA 10.01; re-ran the registration key program and the problem still occurs.

1. Can you send me the sample install project that you successfully built and then installed using the example assembly that I sent earlier? I would like to compare your script to that for my project.

2. I noticed that when I have the Register Assembly checked for each of my application specific assemblies (along with Generate Native Images), that the Native Assemblies do not get generated either but no error message is raised. (I was expecting them to appear in the folder C:\Windows\Microsoft.net\assembly\GAC_32 but they were not present)


The *.tlb files do get generated in the $TARGETDIR$ folder even though this error is raised.

3. I have tried running the install script by just double-click to run and also Run as Administrator and both causee the error.

4. I have manually run regasm against the assemblies after they were installed to the $TARGETDIR$ and they register successfully.

Thanks,
Norm

[giaviv]

Dear Norm,

I am attaching a sample project (with your assembly) that works. Also, I attached the single-exe executable in the Release folder.
Let me know if it works on your machine.

[NormanDerrick]

Hi Aviv,

I did the following:
1. Ran the EXE that you included in the zip file
Installed Ok w/o error

2. Using the script that you provided, re-created the EXE and ran that one.
Install failed.
Would it be helpful if I invite you to my workstation for a GoToMyPC Session for you to check for anything that might be corrupt?

I really appreciate your continuing to assist me here.

Thanks,
Norm

[NormanDerrick]

Hi Aviv,

I have attached the log files from running the EXE that you provided and the log from the EXE that I generated locally (that fails).
Also included in this zip is a screen segment of the point in the log files where they begin to deviate. The left side is from the EXE generated on my workstation and the right side is from the EXE that you provided and works OK.

I don't know if or how the difference affects the results but I thought that it would be helpful to you in determining the issue. It looks like a difference in the permission settings??

Thanks,
Norm

[NormanDerrick]

Hello Aviv,

Have you been able to determine the cause and a solution based on the log files that I provided?

Norm