http://blogs.msdn.com/b/texblog/archive/2007/04/05/linking-native-c-into-c-applications.aspxLast week I saw a question on our MSDN forums asking how to link C++ and C# code into a single binary. It's a scenario that we indeed support (albeit only from the command-line), but as I looked for a reference to which to point this person, I found preciousen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/texblog/archive/2007/04/05/linking-native-c-into-c-applications.aspx#3407942Tue, 19 Jun 2007 19:16:59 GMT91d46819-8472-40ad-a661-2c78acb4018c:3407942Joe<p>Will this (or a similar approach) work for C code as well, or just C++.</p> <p>Thanks</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=3407942" width="1" height="1">http://blogs.msdn.com/b/texblog/archive/2007/04/05/linking-native-c-into-c-applications.aspx#2896367Sat, 26 May 2007 13:14:14 GMT91d46819-8472-40ad-a661-2c78acb4018c:2896367Mayank<p>it would be great to take this some steps further and have a native/managed dll that exposes both unmanaged APIs and managed constructs.</p> <p>One additional advantage would of course be that loading the dll NOT lead to a load of the .Net Runtime in case it is being used by unmanaged code. Though I don't think this is possible as _CorDllMain would be the entry point for any managed/unmanaged IJW/C#/C++ module that you make right?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=2896367" width="1" height="1">http://blogs.msdn.com/b/texblog/archive/2007/04/05/linking-native-c-into-c-applications.aspx#2075795Tue, 10 Apr 2007 21:35:09 GMT91d46819-8472-40ad-a661-2c78acb4018c:2075795Andre<p>You should post this blog entry on Codeproject.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=2075795" width="1" height="1">http://blogs.msdn.com/b/texblog/archive/2007/04/05/linking-native-c-into-c-applications.aspx#2035452Fri, 06 Apr 2007 00:41:54 GMT91d46819-8472-40ad-a661-2c78acb4018c:2035452Steve Teixeira -- MSFT<p>Thanks, Aaron. &nbsp;The al/ilmerge approaches they discuss work well for purely managed scenarios, but they don't support linking native code.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=2035452" width="1" height="1">http://blogs.msdn.com/b/texblog/archive/2007/04/05/linking-native-c-into-c-applications.aspx#2035432Fri, 06 Apr 2007 00:37:40 GMT91d46819-8472-40ad-a661-2c78acb4018c:2035432Aaron Fischer<p>Or you could use ILMerge</p> <p><a rel="nofollow" target="_new" href="http://www.microsoft.com/downloads/details.aspx?familyid=22914587-b4ad-4eae-87cf-b14ae6a939b0&amp;displaylang=en">http://www.microsoft.com/downloads/details.aspx?familyid=22914587-b4ad-4eae-87cf-b14ae6a939b0&amp;displaylang=en</a></p> <p>an example of usage on codeproject</p> <p><a rel="nofollow" target="_new" href="http://www.codeproject.com/dotnet/mergingassemblies.asp">http://www.codeproject.com/dotnet/mergingassemblies.asp</a></p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=2035432" width="1" height="1">