Is VS.NET hardcoded to specific Framework version?

  • Thread starter Thread starter John Cottrell
  • Start date Start date
J

John Cottrell

Hi All,

I have VS.NET 2002 and VS.NET 2003 installed on the same
machine. When I open the 2002 IDE, the About dialog
indicates that I'm using the 1.0 Framework. However, the
about dialog in the 2003 IDE indicates Framework version
1.1.

How do I get the 2002 IDE to use the 1.1 Framework? What
are the ramifications of building an assembly using the
1.0 Framework and then running it on a machine with only
the 1.1 Framework?

Any input is greatly appreciated!

John
 
You can't run a 1.1 project on 1.0 and vice versa per se
In 2003 you can build a 1.0 app
by going into the Assembly Properties and in the build
subitem under General Properties and select either 1.0,
1.1 or both (Select 1.0 if that is what you want to do).
This tab doesn't exist in 2002, and since they didn't know
what 1.1 would look like when they built 2002, I don't see
that you possibly could. I'm 99.9% sure about this.


I hope this answers your question, if not, let me know.

Bill


W.G. Ryan
(e-mail address removed)
www.knowdotnet.com
 
John Cottrell said:
Hi All,

I have VS.NET 2002 and VS.NET 2003 installed on the same
machine. When I open the 2002 IDE, the About dialog
indicates that I'm using the 1.0 Framework. However, the
about dialog in the 2003 IDE indicates Framework version
1.1.

How do I get the 2002 IDE to use the 1.1 Framework?
Click to expand...

You can't. Although you can force the resulting assembly to run only under
the 1.1 framework with the following entry in the app.exe.config.

<startup>
<requiredRuntime version="v1.1.4322"/>
What
are the ramifications of building an assembly using the
1.0 Framework and then running it on a machine with only
the 1.1 Framework?
Click to expand...

None. Should work fine. In fact you should test and deploy only against
the 1.1 framework. This will guarantee that you have a smooth upgrade from
vs2002 to vs2003, and all your different .net apps will play nicely
together.

Again you _can_ deploy both frameworks on a machine, I just wouldn't
recommend it.

David
 
William said:
You can't run a 1.1 project on 1.0 and vice versa
Click to expand...

Please someone tell me this guy is wrong about the vice-versa part. That
would mean that each time a user upgrades their runtime, they would have
to get a recompiled version of all their .Net apps. It would make .Net
development useless for everything except in very controled Windows
configurations.

Alexandre Leduc
 
I think what Bill means is that the Project (Solution) created with VS2003
does not run in VS2003. That is, VS2002 cannot open Solution/Project created
with VS2003, while VS2003 can open Solution/Project in VS2002 and convert it
t VS2003 Solution/Project (and you will not able to convert it back, I
think.). But this does not mean a .NET app compiled in 1.0 need to be
recompiled to run on .NET 1.1.
 
Hi John,

There is a good explanation on this issue on MSDN:

http://msdn.microsoft.com/library/en-
us/vsintro7/html/vxoriWhatsNewInVisualStudioNET2003.asp

Look at the section titled "Side-by-Side Installations of
Visual Studio .NET" and also follow the links "Targeting
a .NET Framework Version" in that section.

HTH,
Donald Xie
 
Yes and no. You can jerry rig VS.NET 2002 to use Framework 1.1. It is very
buggy and spending $29 for the VS.NET 2003 upgrade is a much better option
than dealing with the pain. There are a couple of things that VS.NET 2002
will bomb on in Framework 1.1, as well. I would not advise it.

If you are set on this course, there are threads from earlier in the year
that tell you how to kludge VS.NET 2002 to use Framework 1.1. I would use
news.google.com, if you are really set on this course of action and look
around the March to April time frame.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****
 
If he is talking in the IDE, he is correct. As far as running 1.0 on a 1.1
server, I only have one app (heavy XML) that does not run, right out of the
box. You can do a couple of things to get 1.0 apps running on a 1.0/1.1
server that is set for 1.1, however. one method is the config file, which
works for some apps (dismal in our situation, which is web driven, great for
windows forms); another is to set the particular web app up in IIS to use
1.0

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****
 
There is NO problem having 1.0 and 1.1 on the same box. NONE! I have
multiple web servers serving both without ANY problems.

I would not use VS.NET 2002 to develop 1.1 or VS.NET 2003 to develop 1.0,
but that is where I would stop.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****
 
I concur with you. I would not necessarily test on all versions, unless you
are serving up shrink wrap software (ie, a product for sale, not Enterprise
development). I would have as many versions as you need for developers to
release their apps. Once the 1.0 apps are migrated, I would kill 1.0. No
need to go back.

But, installing 1.0 and 1.1 on the same box, cause absolutely NO problems.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****
 
The config file method is rather dismal in ASP.NET applications, from my
experience. You often have to go into Internet Services Manager and point
the particular app to the 1.0 version on a 1.1 server. With Windows apps,
the target framework suggestion works well.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****
 
Oh, I didn't know that - never had to force a 1.1 app to
use CLR 1.0. Thanks for the heads up. So what you are
saying is that I have to manually change the Application
Mappings if I want to do that - sounds like fun :)

Cheers,
Donald Xie
 
That's what I meant. I never tried moving it back, my
boss didn't want to even take the chance...nor did I.

Using the IDE 2002 couldn't know about MS's intentions in
advance, I guess I didn't communicate it well. ;-(

Sorry about that.
 
Sorry about the ambiguity.

Let me explain. If you have the 1.0 framework and a 1.0
app, then you upgrade to 1.1.. .that doesn't kill the 1.0
runtime. THey both still exist. The first one will
still run. If you look in the registry or your
ADD/Remove Programs and you have 1.1, you'll have both
frameworks installed.

If your code is compiled under 1.1 for instance, and you
reference DataReader.HasRows and you install it under a
1.0 only machine, you'll have issues (at least I did).
That was my point about vice versa. I should have been
more clear.

My apologies.

Bill
 
Amen on all of your posts on this thread!

-----Original Message-----
Yes and no. You can jerry rig VS.NET 2002 to use Framework 1.1. It is very
buggy and spending $29 for the VS.NET 2003 upgrade is a much better option
than dealing with the pain. There are a couple of things that VS.NET 2002
will bomb on in Framework 1.1, as well. I would not advise it.

If you are set on this course, there are threads from earlier in the year
that tell you how to kludge VS.NET 2002 to use Framework 1.1. I would use
news.google.com, if you are really set on this course of action and look
around the March to April time frame.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

********************************************************* *******************
****
Think Outside the Box!
********************************************************* *******************
****



.
Click to expand...
 
Back
Top