I'm hoping to find a .NET/COM interop expert for a general installer question...
I recently came across a .NET assembly that when I call it with regasm
/codebase /regfile it generates a regfile that includes a registry subkey
called Implemented Catagories with a GUID that google tells me represnts a
generic implemented in .NET type.
But what's really special about this assembly is if I run regasm /codebase
without the /regfile and monitor the registry, it actually implements another
registry subkey of Implemented Catagories that has special meaning in the
context of the system.
I was using InstallShields .NET COM = Yes functionality but the developers were
complaining that it wasn't registered. They would then assume it's an
installer problem because if they run regasm on the deployed machine the
expected functionality would stat working.
Anyone ever see anything like this and what would be jacked in .NET to cause
it? It almost sounds like some of the hell I used to see in the COM ATL days.
I can do static extraction but I'm worried it could be fragile in the future if
the details ever change.
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
