How stable is .NET 3.0?

[George Ter-Saakov]

I know it's just an add-on to .NET 2.0. Like more classes added to the
library. And as I understand there is no migration whatsoever. Applications
(ASP.NET ) that worked on 2.0 will work on 3.0 without any additional
tweaking.

So question is if there any problem with running websites after going to
3.0? I would hate to have a downtime for my site.


Thanks
George.

 

[Michael Nemtsev]

Hello George Ter-Saakov,

AFAI, there is no issues, 3.0 didn't affected asp.net.
If you are not going to use .NET 3.0 services from asp.net u needn't bother
about it

you should consider the IIS + platform + SP issues, for example like the
lates Win2k3 SP2 breaks Session_End and etc

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

G> I know it's just an add-on to .NET 2.0. Like more classes added to
G> the library. And as I understand there is no migration whatsoever.
G> Applications (ASP.NET ) that worked on 2.0 will work on 3.0 without
G> any additional tweaking.
G>
G> So question is if there any problem with running websites after going
G> to 3.0? I would hate to have a downtime for my site.
G>
G> Thanks
G> George

 

[Michael Nemtsev]

Hello George Ter-Saakov,

AFAIK, there is no relation between asp.net and .NET 3.0 serives in the asp.net
aspect.
U needn't bother about it, till u use starting using smth from .NET 3.0

I reckon u'd consider IIS + windows + SP issues, coz it seems to be the
weak place. For example, such case as latest SP2 for Win2k3 breaks Session_End


---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

G> I know it's just an add-on to .NET 2.0. Like more classes added to
G> the library. And as I understand there is no migration whatsoever.
G> Applications (ASP.NET ) that worked on 2.0 will work on 3.0 without
G> any additional tweaking.
G>
G> So question is if there any problem with running websites after going
G> to 3.0? I would hate to have a downtime for my site.
G>
G> Thanks
G> George.

 

[Steve C. Orr [MCSD, MVP, CSM, ASP Insider]]

..NET 3.0 is really just .NET 2.0 with some extra classes added in.
The existing .NET 2.0 classes didn't change at all, therefore there aren't
any breaking changes.
There is also no need to upgrade unless you want to use the new
functionality provided by the new .NET 3.0 classes.

 

[Cowboy \(Gregory A. Beamer\)]

I have seen some problems upgrading a 2.0 site to 3.0 on code written by a
partner, so test all of your sites with 3.0 prior to switching your
production server. Other than that, I know of none.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*********************************************
Think outside the box!
*********************************************

 

[George Ter-Saakov]

Thanks
This is an info i am looking for.
Can you go into more specifics. Like what kind of problems.


George.