what you have at the moment is, in .Net terms, "Unmanaged Code" - that
basically means it is a native windows app and does not use the .Net
framework.

The good news is that Visual C++ .net can be used to work with such
unmanaged code in the same way as visual C++ 6, so you should not experience
any problems just upgrading the development environment. However, you will
not be using the .net environment (i.e. not able to access the "built in
stuff" if you do this.

if you actually want to use the .Net framework - i.e. write managed code,
this is less trivial but I'm not qualified to comment on how difficult it is

Andy


"Ashton" <Vonslydog@h...> wrote in message
news:7ffe1f48.0405031308.5155e17d@p......
> Hello all,
> I support a program that was developed in Microsoft's Visual Studio
> 6.0.  A few months ago I added some support for XML message traffic,
> just basic message parsing, validation, and packing.  There have been
> some discussions about migrating our software to Visual Studio .NET.
> I understand that .NET has a lot of XML stuff built into it.  I was
> wondering if anyone could give me some basic info on the
> advantages/disadvantages of switching to .NET from VC++6.0 with
> MSXML4.0.  All we really need to do is parse XML that is read in from
> a byte stream, and pack messages that will be sent out as a byte
> stream.  There are several other factors involved in deciding to
> switch to .NET or not, but from a pure XML standpoint, for the amount
> of XML processing we will be doing, is there really much of a
> difference one way or the other?
> Thanks for any input you might have
> Ashton