Peter et all, Perhaps that is the case in VS2008. I am still in VS.NET 2005 and the IDE didn't set the CLR support to "No Common Language Runtime support". That's OK, I set it manually. I am not after Microsoft to bash them for such bugs - I'd rather try and focus on my work and get this thing done.
Since my idea is to create this Managed C++ library, I suppose I need to leave the /clr compilation option for the project even if I don't have it for my ".C" files. However, I get further into trouble when instantiating structures defined in the C files. I get LNK2028 and LNK2019 when calling the constructor and destructor of such a structure. The structure is created and then destroyed in my only C++ Managed class, the one that I envisioned being sort of the interface to my managed C++ .dll. I can see that the method I plan to export is decorated with __clrcall and rightfully so, since my class is defined into a managed CPP class. But inside, it looks like this is not properly translated into the required __cdecl call, hence all my "unresolved token" and "unresolved external symbol" linkage errors. Any idea how to work around this? Regards, Eddie -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] Behalf Of Peter Ritchie Sent: Wednesday, July 23, 2008 3:51 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Mixing C code in a managed C++ project That's silly, the IDE should do that automatically. I've logged a bug on Connect: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx? FeedbackID=357508 =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
