Register Assembly does not work reliably
Posted: Fri Aug 17, 2007 6:08 pm
I'm using IA 7, and I'm having trouble with the Register Assembly command. My assemblies require .NET 2.0
I am installing the dlls using Install Files (also tried install assembly) because they are NOT going into the GAC, and then I call Register Assembly after Apply Install.
If I install on my Vista machine, my assemblies get registered no problem. On my Server 2003 test machine, they do NOT get registered. I even tried calling regasm directly to make sure it was using the 2.0 regasm and not the 1.1 version (in case that matters). No help. If I call regasm manually from the command prompt, it works fine and my program works fine.
This test machine has had a lot of security related settings done to it (military requirements) which may be affecting this (I'm just guessing here). I'm curious, during install, what user context will programs be run in when I use Run Program or when the Register Assembly command runs? Whichever user launched the install (administrator in my case)? Local System?
Oh yeah, using my old installer built as a Visual Studio Setup project, there is no problem installing on this locked-down system. It works perfectly.
I am installing the dlls using Install Files (also tried install assembly) because they are NOT going into the GAC, and then I call Register Assembly after Apply Install.
If I install on my Vista machine, my assemblies get registered no problem. On my Server 2003 test machine, they do NOT get registered. I even tried calling regasm directly to make sure it was using the 2.0 regasm and not the 1.1 version (in case that matters). No help. If I call regasm manually from the command prompt, it works fine and my program works fine.
This test machine has had a lot of security related settings done to it (military requirements) which may be affecting this (I'm just guessing here). I'm curious, during install, what user context will programs be run in when I use Run Program or when the Register Assembly command runs? Whichever user launched the install (administrator in my case)? Local System?
Oh yeah, using my old installer built as a Visual Studio Setup project, there is no problem installing on this locked-down system. It works perfectly.