C# or C++/CLI?

[Tal Rashas Guardianship]

My project is written by C++, now I want to change it to .NET platform, I have two choices, C# or C++/CLI, choose C# means rewrite all of the code, choose C++/CLI means part rewrite, and it's flexible But I'm warry about three points: 1.The grammar of C++/CLI is surprising, what is the C++/CLI like? C++? C#? a new language? 2.The flexibility of C++/CLI is interesting, but may not good to the project leader, if the programmer write some pure c++ code and cause some abnormal memory accessing, it's hard to find them out. Who can guarantee that his programmers are all good enough? 3.After change to C++/CLI, the workload of refactoring may not lower than rewriting So, it seems that I should use C#? Who can give me some ideas? Thanks in advance

[Paul Conrad]

C# would be the better way to go. I was brought up with C++, went over to C# since I also worked with Java and there are similarities. When C++/CLI came about, I was too hooked on C#. Compare the number of posts in the C# forum here versus the C++/CLI forum...

"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon

[BadKarma]

Hi, In my opinion you should try to stay away from c++/cli. Either choose c++ or C# or like i do: Use C# for gui and stay with c++ for internal processing.

Learn from the mistakes of others, you may not live long enough to make them all yourself.

[Tal Rashas Guardianship]

Yes, the WPF attacked me, I want to use it to the GUI. thanks for your advice