Target 1.1 framework

[Matt F]

I'm pretty sure I've seen this question before, but can't seem to find it
again ---

I've got a project that I'm working on that I'm not going to be able to
migrate to the V2 framework for a little while.so I'm forced to work in
VS2003. I would MUCH rather work in VS2005 and simply target the V1.1
framework --- is there an easy way to do this? If it's a setting someplace,
is it project specific? I have other projects in V2 that I don't want to
screw up.

 

[PvdG42]

I'm pretty sure I've seen this question before, but can't seem to find it
again ---

I've got a project that I'm working on that I'm not going to be able to
migrate to the V2 framework for a little while.so I'm forced to work in
VS2003. I would MUCH rather work in VS2005 and simply target the V1.1
framework --- is there an easy way to do this? If it's a setting
someplace, is it project specific? I have other projects in V2 that I
don't want to screw up.

Have a look at this:

http://www.codeplex.com/Wiki/View.aspx?ProjectName=MSBee

I don't know if it will suit your needs, but there is no internal VS2005
setting.

 

[Linda Liu [MSFT]]

Hi Matt,

The following blog introduces how to build managed applications using
Visual Studio 2005 that target .NET 1.1 step by step:

http://blogs.msdn.com/yaleeyangmsblog/archive/2007/07/05/build-managed-appli
cations-using-visual-studio-2005-that-target-net-1-1.aspx

Hope this helps.
If you have any question, please feel free to let me know.


Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.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/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Cowboy \(Gregory A. Beamer\)]

As long as you do not touch on 2.0 features, you can set up a build script
(can be batch file or MSBee file, as mentioned in Linda's post) for 1.1. If
you touch one 2.0 feature, you are toast.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)

************************************************
Think outside the box!
************************************************

 

[Matt F]

I started getting MSBee set up thought something. I have a concern with
this --- since a command line build is required to generate the assemblies
and there is no IDE support -- I would have to have IIS on my machine
(asp.net app) configured to use V2 of the framework for debugging. I'd be
concerned that I'd get a bunch of work done, get ready to deploy, build with
MSBee and only then find out that I'm unable to build targetting the old
framework.

Any thoughts or suggestions about this?

 

[Linda Liu [MSFT]]

Hi Matt,

Thank you for your feedback!

I would have to have IIS on my machine (asp.net app) configured to use V2

of the framework for debugging

What kind of the application you're going to build, a WinForm application
or a Web application?

I'd be concerned that I'd get a bunch of work done, get ready to deploy,

build with MSBee and only then find out that I'm unable to build targetting
the old framework.

If the application is developed by VB.NET, you should use the
MSBuildExtras.FX1_1.VisualBasic.targets in the project file, i.e. insert
the following line after the "<Import
Project="$(MSBuildBinPath)\Microsoft.VisualBasic.targets" />":

<Import
Project="$(MSBuildExtensionsPath)\MSBee\MSBuildExtras.Fx1_1.VisualBasic.targ
ets" Condition=" '$(BuildingInsideVisualStudio)' == '' AND
'$(TargetFX1_1)'=='true'" />

In addition, the project couldn't contain any keyword or namespace that is
introduced by .NET 2.0 and doesn't exist in .NET 1.x.

Hope this helps.

Sincerely,
Linda Liu
Microsoft Online Community Support\

 

[Matt F]

Linda,

I'm taking maintenance of a c# web application from another. If I
understand correctly, if I follow the steps below, if I attempt to use a
class that is new in V2 and compile I will get a warning and/or error?

 

[Linda Liu [MSFT]]

Hi Matt,

Thank you for your reply.

if I attempt to use a class that is new in V2 and compile I will get a

warning and/or error?

Yes, you should ensure that the project doesn't contain any keywords or
class that is new in .NET 2.0; otherwise, you will get an error.

Sincerely,
Linda Liu
Microsoft Online Community Support

 

[Matt F]

Thanks - sorry for being so particular about this one. The project is
currently in VS2003 and I want to convert to VS2005 --- as you know this is
a one way conversion - I don't want to convert the regret it and realize I
can't go back.

I'll of course back everything up, make the conversion, do a bunch of
testing etc then start working with the project in VS2005 ---- as always,
thanks for your help.