HighTechTalks DotNet Forums  

Why Managed C++ and not C#?

Dotnet Framework (Interop) microsoft.public.dotnet.framework.interop


Discuss Why Managed C++ and not C#? in the Dotnet Framework (Interop) forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
ST
 
Posts: n/a

Default Why Managed C++ and not C#? - 05-21-2009 , 08:19 PM







Hi all

We are about to start a new project from scratch. Performance and
development time are important issues. Thus, we have decided to make
use of .NET with respect to short development time and native
(unmanaged) C++ as the language of the low-level business layer. All
objects of this unmanaged code will be included in a dll.

However, there's one thing that makes me wonder: In order to make use
of .NET, we have to choose between managed C++ and C#, but: What is
the benefit of managed C++ in our scenario?

To make things clearer: Consider an native C++ dynamic class library
allocating memory, making use of C math libraries and performing high
performant calculations. Am I right in thinking that calling this
class by the managed code by

unmanagedScope::BusinessClass* pBs = new std::BusinessClass();

(NOT gcnew) would create performance overhead anyway? If so, the
object must not be created by the managed, but by the unmanaged code,
right? A native wrapper would create the object and pass the data of
the managed stuff. If so, I would not need managed C++ at all and I
would use C# instead.

Do I have missed something? Your oppinions? Hints?

Thanks in advance
ST

Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.