can Framework 1.1 be used with Visual Studio 2003?

  • Thread starter Thread starter Andrew Jenssen
  • Start date Start date
A

Andrew Jenssen

Can any version of .NET Framework 1.0 or greater be used
with Visual Studio 2003? My Visual Studio 2003 shipped
with a copy of .NET Framework 1.0. But I have Framework 1.1
installed currently. Can Visual Studio 2003 be re-installed
with Framework 1.1 to develop apps that run with Framework 1.1?

Jenssey
 
Eh, I'm positive your Visual Studio .NET 2003 shipped with version 1.1 of
the .NET Framework. Version 1.0 shipped with Visual Studio .NET 2002.
 
VS.NET 2003 ships with the 1.1 Framework and creates assemblies that run on
that version by default. You can indicate that you want your 2003 project
compiled to be compliant with the 1.0 framework as well (but the 1.0
framework does NOT ship w/2003).
 
Your're right. I uninstalled VS.NET 2003 and .NET Framework 1.1
(plus its "hotfix") and MSDN Library and re-installed everything.
And... the problem I have persists - the Start Page continues to
point to projects in an old folder, and using Tools/Options/Environment/
General/Projects and Solutions, I still cannot make the entry that
I put in the path window take hold. The result is that when I try to
start a New Project, there's a "DLL initialization routine failed" error.
The same error occurs when I click on My Profile. Apparently,
some registry setting from a course that I took which used VS.NET
2002 software failed to uninstall. I think it was that software which
originally installed the .NET Framework 1.0 (which is not gone, as
far as I know). I may have to spend a couple days re-installing the
entire system.

Jenssey


"CT" skrev:
 
Does one choose that option on a project-by-project basis
or at the time of installing VS.NET? What is the procedure
for choosing the version of .NET Framework?

Jenssey
 
All projects are created to run against the 1.1 Framework and that can't be
changed. If (on a project by project basis) you need to have a particular
project run against the 1.0 Framework, this can be set in the project's
properties dialog.

As for the other problem you mention, it does sound like you have/had a bad
instal/uninstal of VS.NET 2002. But, as an FYI, when you have a version of
the Framework installed and then uninstal the version of VS.NET that used
it, the Framework is supposed to stay installed on the machine. I have the
1.0, the 1.1 and the 2.0 Frameworks all on my machine at the same time.
This is fine and is, by design, not something that you should worry about.
 
To be explicit - you have .NET Framework 1.0, 1.1, and 2.0
*installed* simultaneously on your machine. Is that correct?

And the Visual Studio.NET will also choose which of the
installed versions of .NET Framework to use?

And, supposedly, a C# app developed with Framework 1.0
would indicate to the CLR or Just-in-Time compiler that it should
be compiled/run with Framework 1.0, and the JIT will choose
that version of Framework to do its compiling?

Jenssey
 
To be explicit - you have .NET Framework 1.0, 1.1, and 2.0
*installed* simultaneously on your machine. Is that correct?
Click to expand...

Yes. And, this is, by design, not a problem.
And the Visual Studio.NET will also choose which of the
installed versions of .NET Framework to use?
Click to expand...

Well, not quite. The version of VS.NET you have dictates what Framework
version will be used:

VS .NET 2002 = 1.0 Framework
VS .NET 2003 = 1.1 Framework
VS .NET 2005 = 2.0 Framework

If (and that is a big IF), you wanted to use VS .NET 2003 to build a project
that could run under the 1.0 Framework (not the norm), you could (emphasize
could) via the project's properties, set the target Framework to 1.0 instead
of 1.1, but the situations where you would want to do this would be rare.
And, supposedly, a C# app developed with Framework 1.0
would indicate to the CLR or Just-in-Time compiler that it should
be compiled/run with Framework 1.0, and the JIT will choose
that version of Framework to do its compiling?
Click to expand...

Not quite. Each version of the Framework has its own CLR & JIT Compiler and
the CLR is part of the Framework. It is not independant of it. An
application compiled by a specific compiler version (compilers are also part
of the framework) knows what version compiled it. It isn't up the CLR to
decide which version to use, the application itself knows what version it
needs based on the assembly references it was built with.
 
:
Andrew Jenssen said:
Not quite. Each version of the Framework has its own CLR &
JIT Compiler and the CLR is part of the Framework. It is not
independant of it. An application compiled by a specific
compiler version (compilers are also part of the framework)
knows what version compiled it. It isn't up the CLR to decide
which version to use, the application itself knows what version
it needs based on the assembly references it was built with.
Click to expand...


So the C# appication somehow invokes the correct version of
..NET Framework to run under? And that Framework's version is
the same version that the app was built with?

Jenssey
 
So the C# appication somehow invokes the correct version of
.NET Framework to run under? And that Framework's version is
the same version that the app was built with?
Click to expand...

Yes.
 
Back
Top