Change VS2005 C# project to use mscorlib 1.1

[docschnipp]

I have moved a project from VS2003 to VS2005 and now all references point to
..NET2.0 libs. How can I change this back to 1.1, but still use VS2005?

I need this for compatibility reasons.

thanks
doc

[Laurent Bugnion]

Hi,

docschnipp wrote:

I have moved a project from VS2003 to VS2005 and now all references point to
.NET2.0 libs. How can I change this back to 1.1, but still use VS2005?

I need this for compatibility reasons.

thanks
doc

The only way I know to use Visual Studio 2005 and still compile 1.1 code
is to use MsBee
http://www.gotdotnet.com/codegallery...a-9b8d00970371

However, I never tried it myself. Since you can install both Studios on
a same PC, I think it's easier to stick to the adapted development
environment for the .NET version you're using.

HTH,
Laurent
--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch

[Jeffrey Tan[MSFT]]

Hi Doc,

Yes, Laurent is correct. I have consulted the CLR team before for this
question, they confirmed that there is no native way to target prior
frameworks in VS2005. The only solution to tell VS2005 to use .Net1.1
Framework is using MSBee.

MSBee is an add-on to the MSBuild system that changes the framework
targeted. So, you are actually building against the v1.1 framework using
the VS2003 version of the compilers using the VS2005 version of MSBuild
(sort of). You can write your code in the IDE but must use the cmd line to
do the building, so it doesn't appear to be a seamless integration. You may
refer to my previous support thread below for more information(tak e care of
the line-break):
http://groups.google.com/group/micro...es.csharp/brow
se_frm/thread/5b2c5dfd6bf24aa 2/380ffd947bd7253 1?lnk=st&q=VS20 05+MsBee+%22Jef
frey+Tan%22&rnu m=1&hl=zh-CN#380ffd947bd7 2531

If you wanted to use .Net1.1 for your project, you'd better always use
VS.net2003 to open your project without converting it to VS2005. This will
leave the project working with .Net1.1.

Hope this helps.

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.

[docschnipp]

Hi Jeffrey, Laurent,

""Jeffrey Tan[MSFT]"" wrote:

Hi Doc,

Yes, Laurent is correct. I have consulted the CLR team before for this
question, they confirmed that there is no native way to target prior
frameworks in VS2005. The only solution to tell VS2005 to use .Net1.1
Framework is using MSBee.

MSBee is an add-on to the MSBuild system that changes the framework
targeted. So, you are actually building against the v1.1 framework using
the VS2003 version of the compilers using the VS2005 version of MSBuild
(sort of). You can write your code in the IDE but must use the cmd line to
do the building, so it doesn't appear to be a seamless integration.

Using cmd is okay for me, I'd like to use a kind of build server anyway.
I would really miss the VS2005 IDE with all its nice features.

If you wanted to use .Net1.1 for your project, you'd better always use
VS.net2003 to open your project without converting it to VS2005. This will
leave the project working with .Net1.1.

I can set it up and just refer to the same cs files, that should do?

best
doc

[Jeffrey Tan[MSFT]]

Hi Doc,

Thanks for your feedback.

>I can set it up and just refer to the same cs files, that should do?

Sorry, I am not sure I understand you completely. Yes, for your project
that is already converted to VS2005. You may use VS.net2003 to creat a new
sample project and then add all the cs files back to the new project.

However, actually these steps are no need, since while VS2005 converting
your VS.net2003 project, it will create a "Backup" folder to store your old
VS.net2003 solution. So you may use this backup project for using in
VS.net2003.

If I have misunderstood your 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.

[docschnipp]

""Jeffrey Tan[MSFT]"" wrote:

However, actually these steps are no need, since while VS2005 converting
your VS.net2003 project, it will create a "Backup" folder to store your old
VS.net2003 solution. So you may use this backup project for using in
VS.net2003.

Oh, I wasn't aware of that. I thought there is just a conversion log.
I'll try that,

thanks for your posts,

doc

[Jeffrey Tan[MSFT]]

Ok, if you need further help, please feel free to feedback, I will work
with you. 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.

[Jeffrey Tan[MSFT]]

Hi Doc,

How about this issue now? Does the backup project in VS.net2003 work well
for you? If you still have any concern or need any help, 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.

[docschnipp]

Hi Jeffery,

""Jeffrey Tan[MSFT]"" wrote:

How about this issue now? Does the backup project in VS.net2003 work well
for you? If you still have any concern or need any help, please feel free
to tell me, thanks.

Yes, it worked so far. I tried to use the "new" form1.cs in my old 1.1
project but here I came over another annoying thing: When editing the form in
vs2005, some things are added to the generated code that aren't 1.1
compatible.

I understand that .NET 2.0 is a big improvement but I really wish the
decision would have been to keep more compatibility, but I also understand
that it might have introduced unbearable side effects to Visual Studio as a
product.

Now I know the pitfalls, I can deal with it. It is okay by me now.

Thanks for your help, I'll come up with a new thread if there is still
something left.
doc

[Jeffrey Tan[MSFT]]

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.