Basic Question About Moving From VC 6.0 to VC.NET 2003

[matt.keyes]

Hi all,

If i compile my VC 6.0 code with the VC.NET 2003 compiler (unmanaged
C++), then can the compiled executable be run on a machine without the
..NET architecture?

Thanks!

[Brian Muth]

Yes.

<ma********@gmail.com> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...

Hi all,

If i compile my VC 6.0 code with the VC.NET 2003 compiler (unmanaged
C++), then can the compiled executable be run on a machine without the
.NET architecture?

Thanks!

[Bob Moore]

On 23 Nov 2005 14:02:02 -0800, ma********@gmail.com wrote:

If i compile my VC 6.0 code with the VC.NET 2003 compiler (unmanaged
C++), then can the compiled executable be run on a machine without the
.NET architecture?

Yes. You should be aware that there may be issues if its an MFC
application, because VC7 uses macros that differ from those used in
VC6 (there's less of them). So if you maintain the code in VC7 for a
while then want to recompile it in VC6 (maybe the maintenance
programmer doesn't have VC7, say), you'd have a problem. I gave up
working with VC7 on code that had to be maintainable under VC6 for
partially this reason (I also couldn't stand the IDE of VC7).

That's the only issue I've come across, other than the VC7 compiler
being a bit pickier about adherence to the C++ standard.

--
Bob Moore
http://bobmoore.mvps.org/
(this is a non-commercial site and does not accept advertising)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~
Do not reply via email unless specifically requested to do so.
Unsolicited email is NOT welcome and will go unanswered.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~

[Olaf Baeyens]

> If i compile my VC 6.0 code with the VC.NET 2003 compiler (unmanaged

C++), then can the compiled executable be run on a machine without the
.NET architecture?

Yes and the same is true for VS 2005.

[matt.keyes]

Thanks y'all for the helpful insight!

[RalphTheExpert]

Something to think about ...

I created a completely new (managed) 2003 Forms application.

I sent it off to the client to be tested and it failed immediately with
a nasty crash. The client moved it from machine to machine and it
worked on some but not others.

The answer is: A (managed?) 2003 .Net application has to have the .Net
environment installed. Once we installed it, the application worked
fine.

I'm not happy that the crash did not say anything useful ... like "Hey,
dummy, you need to have .Net installed."

So the question becomes: If you extend your ported (unmanaged) MFC
application with managed code, will you need to have the .Net
environment instaled? Can you resist the temptation to use managed
code?

I don't know the answer to those questions; but I'd particularly like
to get the answer to the first one.

Ralph