http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.pnghttp://channel9.msdn.com/Niners/dark_halmut/Entries, comments and threads posted by Dark_Halmuthttp://channel9.msdn.com/Niners/dark_halmut/en-usTue, 12 Feb 2008 21:06:28 GMTTue, 12 Feb 2008 21:06:28 GMTEvNet (EvNet, Version=1.0.3608.3122, Culture=neutral, PublicKeyToken=null)I have a C# dll built for COM and its all fine for my machine. I have a sample vm setup running just XP, .net 1.1 and 2.0 to serve as a test target machine.<BR><BR>My legacy application is file-server(exe sits on network) and this cannot change. Doing things the right way I install my dll(and interop.xxx&nbsp;files) to C:\Docs and Settings\whatever\App Data\CompanyName\<BR><BR>Now I know I need to get the class into the GAC so that my legacy app can see&nbsp;it over COM. I couldn't do this straight up as the gacutil isnt part of the .net runtime(so the target machine doesnt have it). I wrote a little installer/uninstaller exe which does this using System.EnterpriseServices.Internal.Publish.gacInstall(). <BR><BR>I made sure my dll was strongly typed via the .net command prompt doing sn -k whatever.snk and adding that to the project as the key file.<BR><BR>Ok, I can browse to C:\Windows\Assembly and see my class there but my legacy app still fails when creating the object on the target machine...<BR><BR>What gives? :(<p>in reply to <a href='http://channel9.msdn.com/forums/TechOff/260936-Net-dll-built-for-COM-target-machine-fails/'>.Net dll built for COM, target machine fails</a></p><img src="http://channel9.msdn.com/260936/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" />http://channel9.msdn.com/forums/TechOff/260936-Net-dll-built-for-COM-target-machine-fails/http://channel9.msdn.com/forums/TechOff/260936-Net-dll-built-for-COM-target-machine-fails/Tue, 12 Feb 2008 21:06:28 GMThttp://channel9.msdn.com/forums/TechOff/260936-Net-dll-built-for-COM-target-machine-fails/937http://channel9.msdn.com/260936/WebViewBug.aspx?EVT=0I have a C# dll built for COM and its all fine for my machine. I have a sample vm setup running just XP, .net 1.1 and 2.0 to serve as a test target machine.My legacy application is file-server(exe sits on network) and this cannot change. Doing things the right way I install my dll(and interop.xxx&nbsp;files) to C:\Docs and Settings\whatever\App Data\CompanyName\Now I know I need to get the class into the GAC so that my legacy app can see&nbsp;it over COM. I couldn't do this straight up as the gacutil isnt part of the .net runtime(so the target machine doesnt have it). I wrote a little&#8230;Dark_Halmut3http://channel9.msdn.com/forums/TechOff/260936-Net-dll-built-for-COM-target-machine-fails/RSS/http://channel9.msdn.com/260936/Trackback.aspx