Notice that is a big dangerous, because that only changes the app.config to
allow the execution of the app on .NET Framework 1.0 instead of the default
.NET Framework 1.1 of VS.NET 2003, but since VS.NET 2003 ALWAYS uses and
compiles against .NET Framework 1.1 and can not use .NET Framework 1.0, if
you use some feature of 1.1 not present in 1.0 it won?t be detected at code
or compilation time but at run-time when tested on a machine with .NET
Framework 1.0 alone... so, if you want to play safe, you have to use VS.NET
2002.

Signature
Carlos J. Quintero
MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com
> Open the project in 03, right click on the project in the Solution
> Explorer and choose properties. Then, choose the "Build" category and
> click the "Change" button at the bottom.
Peter Row - 07 Feb 2005 09:21 GMT
Hi,
Thanks for the warning.
Curse, blast and mega-annoyance!%&:
MS if you are reading this:
RELEASE A PATCH FOR THE VS.NET 2002 IDE
Regards,
Peter
> Notice that is a big dangerous, because that only changes the app.config
> to allow the execution of the app on .NET Framework 1.0 instead of the
[quoted text clipped - 8 lines]
>> Explorer and choose properties. Then, choose the "Build" category and
>> click the "Change" button at the bottom.