.Net 1.1 and .Ne 2.0

Saranya B

Hi All... My friend has Visual Studio 2003 and also Visual Studio 2005 installed in her system. Whenever she has to work with VS-2003, she will change the IIS to point the .Net framework 1.1 version and switches to .Net 2.0 when she works with VS-2005 and also she is telling that she has both the framework. What I thought was, to work with both VS-2003 and 2005, it is enough to have .Net framework 2.0 and this 2.0 will have all the features supported by 1.0 and 1.1. We dont install .Net 2.0 as seperate one and only upgrade 1.1 to 2.0. So no need to change the framework. I dont understand why she changes her IIS every time. But I dont change IIS. I just work with both VS-2003 and VS-2005 at a same time. How is it possible? Wht is the concept behind this .Net Framework different versions? Am I making sense? Hope I narrated in a way you can understand. Expecting your explanations for this dbt. Thank You, Saran

N a v a n e e t h

Saranya B wrote:

What I thought was, to work with both VS-2003 and 2005, it is enough to have .Net framework 2.0 and this 2.0 will have all the features supported by 1.0 and 1.1. We dont install .Net 2.0 as seperate one and only upgrade 1.1 to 2.0. So no need to change the framework.

Yes you are correct.

Saranya B wrote:

I dont understand why she changes her IIS every time.

She don't have any other work to do :laugh:

Saranya B wrote:

But I dont change IIS. I just work with both VS-2003 and VS-2005 at a same time. How is it possible?

Because framework 2.0 can support all the libraries available in 1.1. Updating a version means, they won't remove the previous classes. 2.0 is having much more classes than 1.0. Now 3.0 is there. That can support all the classes available in 1.1 as well as 2.0. Hope you understood

printf("Navaneeth!!") www.w3hearts.com

Guffa

VS 2005 has a built in stand-alone web server, so it doesn't need IIS. You can use IIS for 1.1 applications and the stand-alone server for 2.0 applications.

Saranya B wrote:

We dont install .Net 2.0 as seperate one and only upgrade 1.1 to 2.0.

There is no "upgrade" from 1.1 to 2.0. When you install 2.0 on a system that already has 1.1, they will both be available side byte side.

Saranya B wrote:

I dont understand why she changes her IIS every time.

Me neither.

Saranya B wrote:

But I dont change IIS. I just work with both VS-2003 and VS-2005 at a same time. How is it possible?

My guess is that you are using the stand-alone server in VS 2005.

--- single minded; short sighted; long gone;

Saranya B

Thank you Navaneeth!!!

Saranya B

Thanks for you explanation!!!

Guffa wrote:

There is no "upgrade" from 1.1 to 2.0. When you install 2.0 on a system that already has 1.1, they will both be available side byte side.

So, do you mean when we install .net framework 2.0, there will be 2 instances. One with 1.1(which exist already) and another instance with 2.0 version? Can I take your explanation in this way?

N a v a n e e t h

yes u can

printf("Navaneeth!!") www.w3hearts.com

Guffa

Yes.

--- single minded; short sighted; long gone;

RichardGrimmer

DooDooo wrote:

Saranya B wrote: What I thought was, to work with both VS-2003 and 2005, it is enough to have .Net framework 2.0 and this 2.0 will have all the features supported by 1.0 and 1.1. We dont install .Net 2.0 as seperate one and only upgrade 1.1 to 2.0. So no need to change the framework. Yes you are correct.

DooDooo wrote:

Because framework 2.0 can support all the libraries available in 1.1. Updating a version means, they won't remove the previous classes. 2.0 is having much more classes than 1.0. Now 3.0 is there. That can support all the classes available in 1.1 as well as 2.0. Hope you understood

Close, but not quite - there are some pretty major differences between the versions, as my boss would tell you if he were here - he spent an age porting our app to 2.0 hehe

"Knock me down, I'll get straight back up again, I'll come back stronger than a powered up pacman" (Lilly Allen / Kaiser Chiefs)