Hey Simon,
You're probably looking for URLs, but...
This may be the first time in my career that I've heard of a scenario where
you have luxury of one specific target environment, but it's in question
that that environment is a frontrunner option for development?!?!?
From the standpoint of the core technologies alone, the only ways I can see
this even being a real question is if it's two years earlier thant I think
it is and Win2003 is still very new or if we've learned of any glaring
issues it has that 2K/XP didn't. Even in such a case, if you know 2003 is
your target, wouldn't you want to have as much opportunity to know its
pitfalls? What ELSE would MS have been targeting its focus on. There's
becoming some question as to Longhorn, but I can't see how 2003 would've
been anything less than an primary goal for the last few years of .NET.
There are a number of other potential issues like licensing costs for other
software that considers anything running a server version of an OS to be a
server, and therefor priced as such. But from just a .NET and OS
standpoint, your argument should not have to be anything more than stare at
them blankly until they walk away!
- John
"Simon Middlemiss" <Si*************@discussions.microsoft.com> wrote in
message news:9F**********************************@microsof t.com...
We are developing an enterprise class ASP.NET solution, to be deployed on
Windows 2003 Server. I am pushing for this platform to be used as our
general development platform becuase of the differences between IIS 5.1
and
IIS 6.0, however I am meeting resistance from collegues who would like
reasurances that .NET Framework development is not only supported under
Windows 2003 Server, but is recommended. I have struggled to find this on
the web anywhere, and am looking for any help that can be provided.
Cheers
Simon