ASP.NET is the most widely used application development environment within VS.NET.  As such, people waste much time designing and building ways to help them deploy their applications to their web farms (from staging, to QA, to production).

One of Aware Server's powerful features is the ability to package and deploy and configure ASP.NET applications across many machines and may environments. 

Details on how can be found here Aware Server ASP.Net Web Deployment

The following are 5 simple reasons why Aware Server ASP.Net Deployment is 100 times easier and better than any other web deployment tool.

1. Command line vs UI point and click
   1. Aware Server:  Intuitive GUI allows for point, click, run your web.
   2. MS Deploy: learning curve of what commands to do what, then write your script.
2. Setup of tools (remote service)
   1. Aware Server: No tools, just publish, then deploy your ASP.NET application all of the machines at once.
   2. MS Deploy:  msi installation, remote service setup, scripting etc...
3. Versioning
   1. Aware Server:  Publish another version to your environment, then deploy it.  Want to rollback? Just use the Aware wizard and republish your previous version.
   2. MS Deploy: Another script, with hard coded configuration of source/remote machines.  And hope that the old code was saved somewhere safe.
4. Environments
   1. Aware Server: Just deploy your manifest to the environment, then publish.  Then just as you would do with services or business processes, use the Aware Promotion wizard to promote your ASP.NET application to another environment.
   2. MS Deploy:  determine what machines are apart of an environment, write a script that will use those machines, as the environment changes, re-write your script.
5. Multi Machine Publishing
   1. Aware Server:  Just select the IIS machines you want to target and publish, no coding or scripting.
   2. MS Deploy:  You need to know each machine and then develop script to deploy to those machines.