.NET 1.1. and 2.0 on the same computer

[MuZZy]

Hi,

We just closed a release (say, version 7) of our app which was using .NET 1.1 and for the new
release (version 8) we are going to use .NET 2.0. Problem is that we still need to support version 7
for .NET 1.1 and at the same time on the same machine(s) do new development for v. 8 with .NET 2.

If i have both 1.1 and 2 installed how do i switch the current runtime?

Any ideas would be highly appreciated!

Thank you,
MuZZy

 

[Mattias Sjögren]

If i have both 1.1 and 2 installed how do i switch the current runtime?

Each app will by default use the version it was compiled against so
you shouldn't have to do anything.


Mattias

 

[MuZZy]

Each app will by default use the version it was compiled against so
you shouldn't have to do anything.


Mattias

Realy? That's cool! Now i need to convince my boss for which i need to show him anything about it on
microsoft website Do you know if it's writen anywhere on their website? I didn't find anything
about that ...

Thank you,
MuZZy

 

[kolosan]

I have successfully added VS 2005 to my development machine at work and
regularly move between the two (for both small app programming -
currently in 2.0 - and our enterprise ASPX apps - in 1.1).

Any solution created using .Net 2.0 starts in VS 2005 and any .Net 1.1
solution starts automatically in VS 2003. So you needn't worry about
the two co-existing or VS 2005 trying to 'upgrade' the 1.1 solution.

I don't personally know of any Microsoft site which states this but let
Google be your friend

 

[Michael Bray]

Realy? That's cool! Now i need to convince my boss for which i need to
show him anything about it on microsoft website Do you know if it's
writen anywhere on their website? I didn't find anything about that
...

http://msdn.microsoft.com/netframework/technologyinfo/versioncomparison/def
ault.aspx

(watch the wrapping)

This article talks about .NET 1.0 and .NET 1.1 side-by-side execution, but
the answer is basically the same for .NET 1.1 and .NET 2.0. In order to
build/compile .NET 2.0 apps, you should use VS 2005, while in order to
build/compile .NET 1.1 apps, you should use VS 2003. You'll need them both
loaded on your development machine. This isn't a problem as long as you
have the disk space. I have them both loaded, and sometimes I have them
both running at the same time.

-mdb

 

[Michael Bray]

Realy? That's cool! Now i need to convince my boss for which i need to
show him anything about it on microsoft website Do you know if it's
writen anywhere on their website? I didn't find anything about that
...

Here's another one.

http://msdn2.microsoft.com/en-us/library/s80xxs7s.aspx

I found these by searching ".NET side by side execution" on google.

-mdb

 

[Naraendira Kuma R.R.]

--
Naraendira Kumar R.R.
~~~~~~~~~~~~~~~~~~~~~~~~~~~

Realy? That's cool! Now i need to convince my boss for which i need to
show him anything about it on microsoft website Do you know if it's
writen anywhere on their website? I didn't find anything about that ...

Does this help?

http://msdn.microsoft.com/library/d...tml/cpconside-by-sideexecution.asp?frame=true

 

[Dylan Parry]

Pondering the eternal question of "Hobnobs or Rich Tea?", Mattias Sjíµ›í±¥n
finally proclaimed:

Each app will by default use the version it was compiled against so
you shouldn't have to do anything.

What happens if the code to be executed is written within a <script>
block rather than compiled and referenced as an assembly?