Developing modern applications in cloud

If you are getting invalid handler error while running IIS application on local IIS, chances are that you have installed IIS after you installed .Net framework/Visual Studio. The problem is basically IIS by default is not configured to handle ASP.Net files. When you install the Framework, it configures IIS to handle all files for ASP.Net i.e files with extension .aspx, .asmx, .ascx etc. So to fix the error, login as local administrator on your machine. Go to Visual Studio command prompt from Program files. On the command prompt execute following command aspnet_regiis -i Wait for successful installation. Now try again running your application under IIS. This should solve the problem. More information about aspnet_regiis can be found at http://msdn.microsoft.com/en-us/library/k6h9cz8h%28v=VS.100%29.aspx

When you are developing web application using .Net, you have three options for development web server. 1. Visual Studio (2008/2010/2011) has built in development server 2. You can install local IIS (XP Professional/Windows 7 Professional/Ultimate) 3. You have a dedicated development Windows server. You can use any of above three options if there are only few developers in your organisation. However in an enterprise level development, you may want to coordinate code deployment to common development server to avoid overwriting each other’s code. So that leaves with first two options. Option 1 is good if there are restrictions in your organisation on what are allowed to install and you are developing and testing pages at page level. However there are some drawbacks of using ASP.Net development server you must consider. 1. Security Context: By default ASP.Net development server runs in local users security context which has more privileges than a context in which a IIS server o