IT Employment

Ask something
Discussion Locked

And about .NET ???

0 helpful
3 replies

by ladislao

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Ok, some companies are planning the W2k server upgrade but what about the .NET that is comming soon?. Should we start preparing the upgrade from NT to .NET instead of going to W2k first?. Because if we are going to do a mayor change in our server's OS from NT to W2k and later next year from W2k to .NET would it be better to wait a few months and go directly to .NET?

3 replies

by lordinfidel

Right now, you can take 2K and install the .NET framework on it.

Which unless my bearings are off, will probably be what most companies will do anyways.

.NET srvr is still (if I'm not mistaken) in alpha testing. I have not received a beta yetof the real .NET srvr. But I have seen a ton of different types of codename blah blah servers.

In any event, even if they did come out with a pure .NET srvr, I would not even think of deploying it in a production enviroment for at least a year after it has been out publicly (or at least not until the release of the 1st service pack).

I waited until sp2 until we deployed 2K into our production servers. But we also rewrote our code to work on 2K. We are in development now looking at how to migrate into .NET.

But when we do deploy it will be on 2K srvrs with the framework.

by mc_user

Microsoft was due to pull the plug on support for 2000Pro next year, but they recently changed that. The new policy is five years "standard" support with an option to purchase two more years. (If I understand this correctly.)

Check out this article at the register for details.

http://www.theregus.com/content/4/26682.html

This discussion is closed to new replies.