PN: Managed C++ and Unmanaged C++

[Peter Nolan]

Hi All,
I'm interested in the opinion of an expert or two on managed C++.net.

I've been writing cross platform C++ (win/unix) for some ETL tools I
use with clients. All the code is 'unmanaged' as I originally wrote
it in VC++ 6.

I've just completed my first managed code program. I also bought the
book VC++.NET 'Step by Step' Version 2003 and been reading that as
fast as I can. So all this 'managed code' and .net features of C++ are
new to me. I have written vb.net code and read a lot on vb.net and
ado.net.

On first reading it looks to me like:

1. VC++.NET is very closely tied to the win operating system.
2. It is not a trivial process to have unmanaged and managed code
inside the one large batch program.
3. If I was going to convert my code to C++.NET I would be re-writing
it, and then it will not work on unix.
So, it looks to me like the best thing to do is if I want to avail
myself of .net functions I should write code that is only intended to
run on windows and have all the code be 'managed code'. My other code
I should keep a separate copy to run on unix.

Or does someone out there know something about C++.net portability to
unix that I don't know about?

Thanks

Peter Nolan
www.peternolan.com

[Carl Daniel [VC++ MVP]]

At this time, I'd say your conclusions are basically sound, but see

http://msdn.microsoft.com/visualc/ho...a/default.aspx

at some future time, you'll likely be able to run "managed C++" on
non-Windows platforms.

-cd

Peter Nolan wrote:

Hi All,
I'm interested in the opinion of an expert or two on managed C++.net.

I've been writing cross platform C++ (win/unix) for some ETL tools I
use with clients. All the code is 'unmanaged' as I originally wrote
it in VC++ 6.

I've just completed my first managed code program. I also bought the
book VC++.NET 'Step by Step' Version 2003 and been reading that as
fast as I can. So all this 'managed code' and .net features of C++ are
new to me. I have written vb.net code and read a lot on vb.net and
ado.net.

On first reading it looks to me like:

1. VC++.NET is very closely tied to the win operating system.
2. It is not a trivial process to have unmanaged and managed code
inside the one large batch program.
3. If I was going to convert my code to C++.NET I would be re-writing
it, and then it will not work on unix.
So, it looks to me like the best thing to do is if I want to avail
myself of .net functions I should write code that is only intended to
run on windows and have all the code be 'managed code'. My other code
I should keep a separate copy to run on unix.

Or does someone out there know something about C++.net portability to
unix that I don't know about?

Thanks

Peter Nolan
www.peternolan.com