Well, if you have the C++ code and object, the best strategy is to write a managed wrapper in Managed C++. There is a step by step process to do this. You can look in the Migration Guide on how to do this or you can look in my chapter-). This allows the object to be called from any managed language after you do this.
Sam Gentile Co-Author Wrox Professional Visual C++.NET (ISBN 1861005962 ) [EMAIL PROTECTED] www.project-inspiration.com/sgentile http://www.project-inspiration.com/sgentile/DotNet.htm BLOG: http://radio.weblogs.com/0105852/ http://www.project-inspiration.com/sgentile/ScienceFiction.htm -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Thomas Tomiczek Sent: Friday, April 12, 2002 2:48 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Tricks (Managed) C++ issue about COM interop - help appreciated.... Well, (the problem is solved in the meantime, btw). I HAVE the TLBIMP - but I have the COM object "native" as a C++ objhect that I generated. I dont want to go through a CreateObject or a managed new - I awant to create the COM object "directly". Regards Thomas Tomiczek THONA Consulting Ltd. (Microsoft MVP C#/.NET) -----Original Message----- From: Sam Gentile [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 11. April 2002 20:43 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Tricks (Managed) C++ issue about COM interop - help appreciated.... I'm confused. If its COM, just do a tlmimp and generate an RCW. That's your wrapper. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
