Older versions of .NET

[iamleppert]

Hello,

I have some systems that have older versions of .NET framework
installed. The company I am contracting with refuses to update the
framework installed on their machines. Is there any way to switch the
version of .NET you can "compile" in? I have Visual Studio 2005.

The versions they have installed:

2.0.50727.42
1.1.4322.2032
v1.0.3705

Thanks!

Johnathan

 

[Sachin Palewar]

You can install on the machines running 2.0. You said they have 2.0
installed already. If they don't have 2.0 installed on some machines
then you need to use VS 2003 to code and compile.

However why they refuse to install something which is free and useful
is what I don't understand.

Regards,
Sachin Palewar
(Certified Scrum Master)

Palewar Techno Solutions
(Mobile Solutions for Your Business)
www.palewar.com

 

[Scott M.]

However why they refuse to install something which is free and useful

is what I don't understand.

Because client installations can be very time consuming, cause yet one more
application that may need updates/support and could cause unanticipated
conflicts with other software on the system.

Just because something is free and useful doesn't mean it's a no brainer
when it comes to installing across the enterprise.

 

[Norman Yuan]

They have already had all .NET version installed: .NET1.0, 1.1 and 2.0
(except for .NET3.0, which is add-on the .NET2.0 and you really cannot do
much with it using VS2005 yet).
So, what is the problem, if you use VS2005, which requires .NET2.0?

 

[Rad [Visual C# MVP]]

Hello,

I have some systems that have older versions of .NET framework
installed. The company I am contracting with refuses to update the
framework installed on their machines. Is there any way to switch the
version of .NET you can "compile" in? I have Visual Studio 2005.

The versions they have installed:

2.0.50727.42
1.1.4322.2032
v1.0.3705

Thanks!

Johnathan

There was a Visual Studio Addin called MSBee to allow you to compile
applications targetting the older .NET framework

 

[Jonathan Boivin]

Otherwise, you could use the command line compiler which is coming with each
version of .NET. Though, you have to make sure that when you code in VS.NET
2005 that all your references to System are suppported by the version you
want to compile to.

The compilers are availaible in the folder :
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 (which here the version number
depends on the one you want to compile to)

For VB.NET it is vbc.exe and for C# it's csc.exe.

Have good luck,
Jonathan Boivin

 

[iamleppert]

You can install on the machines running 2.0. You said they have 2.0
installed already. If they don't have 2.0 installed on some machines
then you need to use VS 2003 to code and compile.

However why they refuse to install something which is free and useful
is what I don't understand.

Regards,
Sachin Palewar
(Certified Scrum Master)

Palewar Techno Solutions
(Mobile Solutions for Your Business)www.palewar.com





- Show quoted text -

Hmm, I am getting an error message when trying to run a test app
stating I must have some .NET framework installed. I'll have to get
the exact error message and research further. They are refusing to
install because basically they have a very backwards IT department.
Changes to user machines involves an IT person manually going from
station to station. Needless to say, a very time consuming and labor
intensive process. I offered to automate the installation but they
just don't see a need to accomodate me (since I am working for them).

Thanks for the help all.

 

[Guest]

I have a followup question on this.

Context:
I'm a SQL Server contract developer who is trying to learn C# and .Net while
I am between projects. I have two machines I can configure for training.
Since I don't know who I'm going to contract for next, I want to learn both
..Net 1.1 and 2.0. I currently have Visual Studio 2003 but can get a copy of
2005.

How many of the following statements (if any) are true?

1. Any machine can execute programs built under either .Net 1.1 or 2.0 as
long as the appropriate frameworks are installed.

2. Visual Studio 2003 will only recognize .Net 1.1.

3. With Visual Studio 2005 you can code against either 1.1 or 2.0 but you
will have to use the command line compiler to get the right version.

4. If you have both 1.1 and 2.0 SDKs installed, Visual Studio 2005 will only
show Intellisense prompting for 2.0.

If all of the above are true, I can configure one machine with VS 2003 and
1.1, and the other machine with VS 2005, 1.1 and 2.0. Then everything I
develop will execute on the second machine, and I can still get
version-correct Intellisense prompting by using the different development
environments.

 

[Scott M.]

1. Any machine can execute programs built under either .Net 1.1 or 2.0 as

long as the appropriate frameworks are installed.

Any Windows machine.

2. Visual Studio 2003 will only recognize .Net 1.1.

Well, sort of. You can build 1.0 applications with VS .NET 2003, but 1.1 is
the standard.

3. With Visual Studio 2005 you can code against either 1.1 or 2.0 but you
will have to use the command line compiler to get the right version.

I don't think so, I think you can compile for the version you want via a
project setting (just as you can choose 1.0 or 1.1 in VS.NET 2003).

4. If you have both 1.1 and 2.0 SDKs installed, Visual Studio 2005 will
only
show Intellisense prompting for 2.0.

SDK has nothing to do with it. VS.NET only shows what the 2.0 Framework
has.

If all of the above are true, I can configure one machine with VS 2003 and
1.1, and the other machine with VS 2005, 1.1 and 2.0. Then everything I
develop will execute on the second machine, and I can still get
version-correct Intellisense prompting by using the different development
environments.

You can install everything on one machine without problems. The different
frameworks sit side-by-side as do the different VS.NET versions.