mixing managed environments

[BilfFord X]

I'm trying to update my ability to make something happen in a windows
environment and find that a lot of water has gone under the bridge.
Apparently, in today's dot net development as opposed to VS6, a fella can
mix managed and unmanaged c++. q1) Is that something a prudent person would
do unless he's got a mountain of legacy c++ code to worry about? q2) Does
it change the answer if, instead, he has legacy c code or really good
reasons not to cut and run from c completely? cheers, bfx

[Nicholas Paldino [.NET/C# MVP]]

BilfFord X,

If you have a solid unmanaged code base which does what you need it to
do, is tested, and doesn't need to be updated, I would see little reason to
actually re-write that code base in managed code. If anything, I would
interop with it, through the P/Invoke layer, COM interop, or by creating
managed wrappers for it.

If it ain't broke, don't fix it.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"BilfFord X" <in*****@invalid.nyetwrote in message
news:44***********************@news.usenetmonster. com...

I'm trying to update my ability to make something happen in a windows
environment and find that a lot of water has gone under the bridge.
Apparently, in today's dot net development as opposed to VS6, a fella can
mix managed and unmanaged c++. q1) Is that something a prudent person
would do unless he's got a mountain of legacy c++ code to worry about?
q2) Does it change the answer if, instead, he has legacy c code or really
good reasons not to cut and run from c completely? cheers, bfx