Tell me why I should upgrade to 2.0

[eyeswideclosed]

We have about 10 very large (many hundreds of pages) heavily loaded (2000+ sessions a day) interconnected .net apps running under 1.1, everything runs very smooth and fast, never a hiccup. We had compelling reasons to upgrade to .net from classic asp, but I see none now. I converted to 2.0 on one of my test servers and had lots of problems right off the bat. Management will not cease new requests to give me time to upgrade anyway. Keep in mind these are very large legacy applications with many thousands of lines of code that has been battle tested. Why should I upgrade?

 

[chrissie1]

No reason what so ever.

Christiaan Baes
Belgium

"My new site" - Me

 

[eyeswideclosed]

Serious? Thank you!

 

[chrissie1]

Actually. If you start a new project just do it in 2.0. You will love some of the new things. But converting a good project to 2.0 would be a waste of time in my opinion. I would at least wait for SP1.

Christiaan Baes
Belgium

"My new site" - Me

 

[eyeswideclosed]

Yeah but 1 problem I found was that a page in a 1.1 app has problems calling a 2.0 page, they both have to be 2.0, I don't know why this is happening here but it was enough to scare me off for now. Anyway I have always said it's the carpenter not the toolbox, I've seen improperly written 2.0 apps crash servers.

 

[chrissie1]

I agree. And it would take time to rewrite and retest.

Christiaan Baes
Belgium

"My new site" - Me

 

[eyeswideclosed]

Thanks for the input guys/gals.

 

[chrissie1]

Perhaps you should wait for some of the smarter kids to say something on the subject.

Christiaan Baes
Belgium

"My new site" - Me

 

[eyeswideclosed]

I'm sure there are those that will talk about all the great new toys available, but this is a huge amount of legacy code that has been upgraded and added to going back 9 years, our latest conversion was from asp 3.0 to .net 1.1, that took 6 months, it is running absolutely perfectly, why would I want to mess with it? The basic design and core components will not change anyway. And when I say battle tested I'm not exagerrating, this system gets pounded all day every day and just purrs, what if I were to introduce some instability by upgrading? Just can't see a reason.

 

[jshurst]

Yeah but 1 problem I found was that a page in a 1.1 app has problems calling a 2.0 page,"

Do you mean in the same virtual directory or do you mean in general? You probably know this, but they can not be in the same virtual directory because you must specify which version of the framework you want to use.

Oh one compelling reason...because everyone else is doing it! j/k I wouldn't want to convert all of those pages. I agree with Christiaan.

 

[eyeswideclosed]

They are separate apps in separate directories, they call each other (response.redirect), but they have to be running the same framework version to work together I noticed, get the big red "app not available" error otherwise, weird huh?

 

[eyeswideclosed]

Isn't quality code more important than what version of whatever you're running it on? If I write crap code will it run better on 2.0?? Tell me I'm wrong!

 

[tperri]

you're wrong.

(You said to TELL you that. not that I believe that)

 

[eyeswideclosed]

 

[BoulderBum]

.NET 2.0 performs better and will probably help future maintainability (if that's an issue) because of its richer features, but I'm with everyone else. There doesn't seem to be a compelling reason to change based on what you said.

 

[ca8msm]

I agree - for any new apps use 2.0 but from the info you've given there doesn't seem to be any reason for you to upgrade your existing ones.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[chrissie1]

Jeez, thats new, everyone agrees with me.

Christiaan Baes
Belgium

"My new site" - Me