Jump to content

Recommended Posts

Posted

Im in the middle of making my unattended CD for Sept 07 over the holiday and would like to try and slim the CD down.

 

Ive got .NET 1.1 / 2.0 and 3.0 but will .NET 3.0 do everything below? I've heard the Aug SIMS update requires 3.0.

 

Cheers!

Guest metalmonkey
Posted

The Dot Net's are not backward compatible. If you have an application that needs v1.1 then you'll need v1.1 installed despite having v3.

 

You might as well put v3 on anyway.

Posted
Each .Net has its own slightly different API (eg. there are calls which don't exist in 3.0 which do in 1.1 as they have gone through depreciation and have been removed) so you end up having to install all 3. Each one kind of supplements the prior ones in a way.
Posted
Remember VB Virtual Machine - VB5 Apps Need VB5VM, VB6 Apps Need VB6 Virtual Machine, VB7 Apps (or VS.NET 2003 Apps) need .NET 1.1, VB8 (or VS.NET 2005 Apps) need .NET 2.0, and VB9 (or VS.NET 2008 Apps) need .Net 3.0, each one is a slightly different language. Also .NET 3.0 includes things like WPF, and WCF.
Posted
The Dot Net's are not backward compatible. If you have an application that needs v1.1 then you'll need v1.1 installed despite having v3.

 

You might as well put v3 on anyway.

 

It's more a case that the v3 installer will install v2 if it's not already there. Capita advise schools to install v3 as it will be used in about 18 months time. So save yourself the return trip now.

Posted

Btw if you install .net 2.0, .net 1.0-1.1 apps WILL run with it

From MS: http://www.microsoft.com/downloads/details.aspx?familyid=9655156b-356b-4a2c-857c-e62f50ae9a55&displaylang=en

The Microsoft® .NET Compact Framework 2.0 Redistributable contains the common language runtime and class libraries built for the .NET Compact Framework. In addition to supporting version 2.0, it also supports applications developed for version 1.0 and service pack releases before version 2.0.

 

There are some very rare apps that use 1.0 commands that were not ported and could have runtime issues.

If you look at:

http://msdn2.microsoft.com/en-us/netframework/aa570326.aspx

it will let you see what breaks runtime but I think it would run fine (all our .net 1.0-1.1 apps run using only .net 2.0)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...