Hi Doc,
Thanks for your feedback!
Oh, I am not sure I understand you completely. I assume you are using
VS.net2003 for the backup 1.1 project. Then why will the VS2005 affect this
1.1 project?
Yes, I see your concern over VS2005. The .Net2.0 has tried to keep the
maximize backward compatibility with .Net1.1, if you are curious, please
refer to the link below for more information:
"Testing compatibility for Whidbey/Everett"
http://blogs.msdn.com/danielfe/archi.../03/51921.aspx
However, there are still some breaking changes in .Net2.0:
"Breaking Changes in .NET Framework 2.0"
http://msdn.microsoft.com/netframewo...nges/default.a
spx
VS2005 is a different development environment from VS.net2003; it uses
different project/solution model and file organization model. It leverages
the partial class introduced in .Net2.0 to separate the designer code
totally from the form level business logic code. This file separation has
the advantage of improving development performance, however, it introduced
the imcompatibility with VS.net2003. So, on my daily life, I normally still
use VS.net2003 to open/code/build .Net1.1 projects/solutions and use VS2005
for .Net2.0 new projects. It will works well without affecting each other.
Additionally, the best solution is using "Microsoft Visual Studio Version
Selector" to open the "*.sln" file, the sln file will be openned with
correct VS version it previous uses.
Hope this makes sense to you and thanks for your understanding. If you have
any further concern, please feel free to tell me, thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.