C++/CLI or C#

[Guest]

Hi all,
I'm trying to decide in wich language I' m going to write a set of
tools and a Windows desktop application so I think that ".Net" has what I
need. My background knowledge is in Visual C++ but I don't know if it's
better to write it in C++/CLI or in C#. I know that some differences are on
my taste/background, if I want to migrate code or reuse it or if I want to
mix managed and unmanaged code but I'd like to know your opinions about
C++/CLI.
Is it the way to go for a C++ developer that wants to use .Net?

 

[G Himangi]

If your primary experience is C++, then C++/CLI should offer a much smoother
transition to the .Net framework. That said, with C++/CLI, the two languages
are now extremely similar syntax-wise.


---------
- G Himangi, Sky Software http://www.ssware.com
Shell MegaPack : Drop-In Explorer GUI Controls For Your Apps (.Net & ActiveX
Editions Available)
EZNamespaceExtensions.Net : Develop namespace extensions rapidly in .Net
EZShellExtensions.Net : Develop all shell extensions rapidly in .Net

 

[William DePalo [MVP VC++]]

I'm trying to decide in wich language I' m going to write a set of
tools and a Windows desktop application so I think that ".Net" has what I
need. My background knowledge is in Visual C++ but I don't know if it's
better to write it in C++/CLI or in C#. I know that some differences are
on
my taste/background, if I want to migrate code or reuse it or if I want to
mix managed and unmanaged code but I'd like to know your opinions about
C++/CLI.
Is it the way to go for a C++ developer that wants to use .Net?

To some extent this is religion we are discussing not technology. That said,
as I see it, C++/CLI is the way to go when your application has feet on both
sides of the managed / unmated divide. Strictly native things are more
easily done in C++, strictly managed things in C#. There is no law that says
you can't create a solution with assemblies of both types.

Regards,
Will