I currently have a .NET 2 assembly which is going to be distributed as part of our next software release. As it needs to be registered for interop I run regasm /regfile to get the registry entries that I then import into my install.
However, it also contains InterfaceIDs which regasm doesn't output when used with /regfile (see http://msdn2.microso...yw6(VS.80).aspx for more info).
The only way I can currently see of doing this step is to have a custom action in my install that calls regasm /tlb on the dll, but if possible I would live to avoid this step.
I feel like there must be a way and I'm missing something obvious, any help is appreciated.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Registering assemblies without using custom action
Started by rmatheson , Jul 16 2007 16:05
1 reply to this topic
Posted 18 July 2007 - 11:01
I'm being a muppet - The correct way of doing it is to include the tlb as a seperate file in the install, and extract the registry entries at build time and include them with the tlb component.