Mass Infection of IIS/ASP Sites (opens in new tab)

ASP.NET is an extremely full-featured, well-tested, and carefully designed enterprise web stack.

What you're really asking is, why would you deploy on an enterprise stack as opposed to a modern app framework. There's lots of reasons, none of which will be congenial to you:

* A much larger pool of available developers

* Better enterprise integration features (depending on your platform, J2EE or ASP.NET may be predetermined for you)

* Better security controls (single signon, LDAP integration, permissioning, etc)

* A preexisting deployment platform that new ASP or J2EE apps can be rolled out onto.

There is really no good reason to do a web startup on ASP.NET or J2EE. So the short answer to your question is, "no, none of us should be using it." But there are lots of valid reasons for businesses to use it.

Is this a real question or a silly jab at Microsoft? I think you're underestimating the number of existing businesses who have .NET at their core, in which case the question is what justifies moving off of .NET? In my experience .NET can be - while not as hip - a very solid framework.

More like: "Management Drank the MS Kool-Aid"

If your boss says you must use IIS then not much you can do.

You use IIS because you want to use ASP. You can't replace ASP with Nginx, it's an entire development stack, not just a webserver. And I actually like ASP. It's fast, easy to develop with, easy to deploy and there's great library support.

Good ms office integration. Thats interesting for many customers. Many customers also have IIS-Servers because office integrates good into these.

Good ms product integration in gereral should also be a valid point.

Also if a company has gotten into the above some time back, when asp on iis servers was the only way(?) for enterprise office integration for large reporting systems, it's easier to let the asp developers learn asp.net and integrate the old enterpise systems with the new. When the old systems are rewritten, asp.net is the way to go, because the customer already has large parts of the infrastructure.

If you're deploying an app in to an enterprise that is already running an AD environment with other Microsoft products like SharePoint, Exchange, Office, and Microsoft Dynamics, it makes a lot of sense. I'm a Mac user and our startup is a kool-aid drinkin' Ruby on Rails shop, but I have administered enough large networks to see the power and value of Microsoft in the enterprise. Like it or not, the integration between Windows clients, Windows servers, and Microsoft applications is pretty incredible.

By using SPs you more or less double the effort to port your application away from whatever database you are using.

Better to use an ORM.

Stored procedures aren't even required. Just use parameterized queries.

You know...if it were that easy then this would be a solved problem. But it isn't that easy, especially in large, enterprise environments.