This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Regasm not running during install
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 04, 2010
03:59 PM
Regasm not running during install
We added a new .Net dll. We already added interop assemblies from unmanaged code to managed code. This is the opposite, managed code to unmanaged code.
This is an InstallScript project.
Under options I've already set the RegAsm.exe path and set the default to Properties and Dependencies. The component's (to which it had it's own component) .NET Settings is set to "Local" and "Dependencies".
The problem is that this new component installs CORRECTLY on everyone else's system except one (this one is used to write manuals and is a clean machine). We found out that the dll is not being registered (via RegAsm). We have a sneaking suspicion that their .NET installation is messed up. We tested this by using another person's version of RegAsm.exe (yes we are using v2....). The dll is not being registered.
Are there any way to verify that this is being registered (meaning is there a way to find out if it is using the correct RegAsm and/or it's returning an error)?
This is an InstallScript project.
Under options I've already set the RegAsm.exe path and set the default to Properties and Dependencies. The component's (to which it had it's own component) .NET Settings is set to "Local" and "Dependencies".
The problem is that this new component installs CORRECTLY on everyone else's system except one (this one is used to write manuals and is a clean machine). We found out that the dll is not being registered (via RegAsm). We have a sneaking suspicion that their .NET installation is messed up. We tested this by using another person's version of RegAsm.exe (yes we are using v2....). The dll is not being registered.
Are there any way to verify that this is being registered (meaning is there a way to find out if it is using the correct RegAsm and/or it's returning an error)?
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 05, 2010
02:15 PM
Not that it matters...
The issue was due to a bad .NET install on the client's machine. The messed up install screwed up registration (with RegAsm). This screw up cause our application to crash whenever the .NET dll was called. The reason our older .NET application worked fine (I know I didn't add that to the original post) because it must have been registered with the older RegAsm.exe. Chances are is that .NET install only worked for older .NET applications meaning the newer version that executes newer .NET code was bad...
So the fix was to have the client reinstall .NET (3.5 SP1).
The issue was due to a bad .NET install on the client's machine. The messed up install screwed up registration (with RegAsm). This screw up cause our application to crash whenever the .NET dll was called. The reason our older .NET application worked fine (I know I didn't add that to the original post) because it must have been registered with the older RegAsm.exe. Chances are is that .NET install only worked for older .NET applications meaning the newer version that executes newer .NET code was bad...
So the fix was to have the client reinstall .NET (3.5 SP1).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 05, 2010
08:08 PM
What project type is this?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 08, 2010
07:27 AM
InstallScript.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 08, 2010
07:53 AM
Consider using REgasm /regfile:foo.reg foo.dll to generate a regfile that you can then import into installshield. This way you don't have to call regasm during the install, you just lay down the registry information.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 08, 2010
08:00 AM
But would that fix the issue?
Would the fact that a bad .NET install might/would cause larger issues throughout the entire application?
I mean that is a work around that I most likely will enter into the install as a precaution...
Is there a way to create a regfile for normal dlls that do not use .NET? and is there a chance the CLISIDs would be duplicated? Because the regfile would be a good way to make a repair script in case the user has issues with the registration.
Would the fact that a bad .NET install might/would cause larger issues throughout the entire application?
I mean that is a work around that I most likely will enter into the install as a precaution...
Is there a way to create a regfile for normal dlls that do not use .NET? and is there a chance the CLISIDs would be duplicated? Because the regfile would be a good way to make a repair script in case the user has issues with the registration.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 08, 2010
10:54 AM
I understand the desire to be premptice but you can't be responsible for platform issues especially if they occur after installation. Read Aaron stebner recent blog post about what happeneds to intuit when they did this type of check.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 08, 2010
11:06 AM
No it's more for scripting the repair procedure. I don't want to fix environmental issue as we've seen with this issue. More like a brute force fix...
