C# or C++/CLI ??

GRRRRRRRRRRRRRRRRR!!!!!!!!!!!!

Im so double minded on whether to go with C++/CLI or C#. I dont know what to do.. :(

Any advice guys

Im looking to develop Windows Forms App's with Power and ease. I have C++ Knowledge but seeing that there arent many resources for C++/CLI, im thinking about going with C# like the many C++ Programmers out there who are...Not that i dont like C++/CLI or C++, its just that C# is a "pure" .NET Language and will always be supported by Microsoft.I also feel as if im being left out of the crowd by continueing with C++/CLI seeing that C# is what many C++ Programmers are moving to.

Visual C++16

C#, for me. I have a C++ background, but managed C++ was a nightmare ( and now it's gone ). In the meantime, I've built my C# skills so that I am quite happy to use it, and to use C++/CLI for wrappers, etc. Having said that, there is some stuff in C++/CLI that looks pretty cool ( such as deterministic destruction, sort of ), which makes it look good, but I still think for GUI programming, C# is better, and certainly more widely supported.

Hi,
in my opinion, the language isn't the most important thing to learn. Learning the framework, learning design patterns, algorithms, structuring your programs, etc. are more important than the language. Of course without a language you couldn't put these in pratice but it's just a mean to get to an end.

It's also important to know what the language has to offer but if you know c++ well, it will be very easy to jump either to c# or c++/cli. Here you can find useful information if you decide move to c#: http://msdn.microsoft.com/msdnmag/issues/01/07/ctocsharp/

If I were you and didn't have any particular reason to choose c# or c++/cli then I would go for c#. The code is cleaner, i.e., easier to read and you don't have to worry with "#includes" :). Visual Studio is also better prepared for c#.

Thanks for the tips guys. Looks like im going onto C# then :D

To tell you all the truth, im happy i took the C# road, and cant wait to get started with it , and thanks for the link n0n4m3, really helped me.

btw, a quick question: Do i need to learn some of the fundamentals of C#(for console apps) first before moving onto VISUAL C# .NET or am i fine by just jumping onto Visual C#.NET and RAD Development

Thanks again

C++/CLI also has its own benefits.

Take a look at http://www.codeguru.com/forum/showthread.php t=391694, http://www.codeguru.com/forum/showthread.php t=391429, http://www.codeguru.com/forum/showthread.php t=391421& http://www.codeguru.com/forum/showthread.php t=391574

Thanks,

Ayman Shoukry

VC++ Team

I made the thread for the first link you gave

.I also agree that C++/CLI has its own benefits.

For statistics: I agree with cgraus. In my work I try to do whatever is possible in C#, C++/CLI remains for interoperability and accessing legacy C++ code. For me, it works fine, I beleive I use best features of both languages.

Just picked up a copy of "Microsoft Visual C# 2005, Step by Step".Gotta say that alot of things can be done quicker in C# than in C++, also alot easier.

IntMain, unless dependencies and performance concerns become a concern, I'd go with C#. But knowing both languages is even better. One of my projects is in C# and C++ with C++/CLI in between.

Brian