>
That could be why companies woudl decide not to go with the MS solution. Changing the name of an OS does not add to the confidence level that many have in Windows software.
>

There is no question that many companies have not used MS server solutions. The fact is, .Net servers have been around (SQL Server, IIS, etc...) The only difference is the name. With that said, there are A LOT of companies who have elected and will continue to use MS server solutions. As far as IIS is concerned, alot of the security issues result from the way IIS has been implemented and whether the company has kept up with the patches. I grant you that IIS is not perfect. However, if one uses some common sense and uses best practices, the issues with IIS are largely obviated. Security issues are a full time job. It is not something you can set up and forget. This is true regardless of the server software you use...


>
Like I said, my guess is that the decision makers don't care too much about the nice objects in the MS solution. All they know are the horror stories related to IIS. If they decide on a platform for their web services, the server is probably going to be more important than the neat objects MS gives you to develop against. JMO.
>

I think the horror stories with IIS are largeley over-blown. Yes, there have been problems - but a lot I contend are due to ways IIS is implemented. Further, it is not as if other servers such as Apache, etc have not had security problems...

Decision makers DO care about the tools developer's use. If this were not the case, VFP would be more prevelant. There is a distinct and recognizeable bias toward developer tools. And, MS is pushing VS .Net heavily. Say what you want about MS marketing - in the end - it is very effective...

>
We're not talking about Desktops here, which is what changes with .NET. Now, we're talking about a server, and a device. Not always a PC.
>

MS recognized that abandoning the desktop was a bad idea. The compelling story in VS .Net are windows forms. There was a distribution problem with windows apps. VS .Net solves a lot of that problem. Now, you will get the rich windows interface with the ease of distribution that a web-app enjoys..

>
Haha. You can tell you're doing something right technologically (MS) when the only way to be beat is politically (Sun and friends).
<

The bottom line is that Sun technology and the related folks - is very complicated and expensive to implement. TCO is a big issue - and one that MS wins hands-down. Look at implementing a Novell network vs. an NT network. The cost to maintain and implement a Novell Network is roughly 10x that of an NT/2000 network. A NT/2000 network is a lot easier to implement as well. Ever try setting up a Unix server? It is a complicated PITA!


The war is over---all that is left is the crying...