Disabling CLI and Managed C++

[mlgoff]

Our company is looking at upgrading to VS 2008 from VS 6.0. Almost all of the work we do is for non-Intel embedded processors. Out biggest concern is ensuring that our developers don't accidentally include any form of Managed C++ or C++/CLI in our target code.

Is there a compiler switch or MACRO that will disable Managed C++ or C++/CLI and cause an error to be generated if a developer tries to use Managed C++ or C++/CLI?

[ahoodin]

Well C++ CLI is a seperate syntax.

Whats to stop someone from pasting some PASCAL into their C++ project?

Common sense mostly.

Managed C++ is similar, except there are standard ways to make code managed and unmanaged. Compiler switches, and garbage collector macros.

There is no substitute for experience and knowledge, but there probably would be some proprietary macros you can develop if you really wanted to. Mostly I suggest code reviews and disabling copy paste for new employees.

[mlgoff]

Thanks for the information. I've never even looked at C++/CLI so I didn't know the syntax was significantly different.

We do code reviews and monitor our interns closely but it would save time (and hence money) if the compiler generated errors whenever Managed code was used.

Would you happen to know where I can get list of the compiler switches used to disable managed code and garbage collectors?

[ahoodin]

Here is a good description.

http://en.wikipedia.org/wiki/Managed_Extensions_for_C++

HTH,

[mlgoff]

Thank you very much!