Hello. I am a bit confused by the behaviour of this option available from the Properties context menu for a .net assembly file I am delivering as part of my setup.
Does it actually cause regasm.exe to be run on the target machine where the setup is being installed?
I think it must be interrogating the assembly on the build machine, because the registry settings for the assembly are displayed in the 'registry' page of AI, but does it also run regasm at install time, or does it just copy in those registry settings it has detected at build time?
On a related issue, I have a 32-bit setup project and a 64-bit setup project. However, if in the 64-bit setup project I set up regasm.exe in the "External Tools" dialog to point to the 64-bit regasm, if I then switch to my 32-bit setup project, this also now points to the 64-bit regasm, i.e. the setting is not stored per-project. Which seems to make it difficult to build both 32 and 64-bit setups that deliver .net asemblies that need registering, on the same build machine?
FOLLOW US
Get the latest news in Application Packaging