Quote:Original post by Anonymous Poster

Quote:Original post by Emmanuel Deloget
@Anonymous Poster: if writing new code in C++/CLI is a Bad Idea, how do you migrate the code you wrote in unmanaged C++ to your managed code base? You discard it and rewrite it in C#, trying to keep your customer happy while you are wasting his money?

Hi. I think you should read the post again, since you obviosly missed the point of it. "New code" isn't old code you are moving to .NET, new code is... NEW CODE. If you read the post again, you will notice that I said the only thing it's good for is migrating existing C++ code to .NET.

You'll typically leave your C++ codebase intact, meaning that you'll have to write the glue between your C++ components and your C# components. What kind magic of truely amazing magic do you use if you achieve to do this without writing new code?

The situation is the same when you just bought a C++ DLL and want to create a managed interface for this DLL. In this case, it is even more clear, as you didn't wrote the code of the DLL - thus, you still end up by writing new code.

Another situation that can arise is that you want to stress the last bits of your computer and you don't trust the CLI. You need "teh fastar" C++ (maybe with mixed asm), but you'll provide some glue to mix you code withing your managed application.

Whenever you have to create some software between a C++ code base and a managed software, you need to write new code - and C++/CLI perfectly fit the bill, as it has a foot in both worlds. You are perfectly free to ignore that. But don't tell us that C++/CLI is a dead beast - or if you do, provide sources. Without them, it is just another absurd AP claim.

Regards,