Skip to main content

What is the difference between ASP.Net Development server and IIS?

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 or local IIS runs. This means the applciation running in ASP.Net development server may have more permissions to resources like files, registry, database or even code access security. Often you find that these application fail when deployed to IIS server.
Also if you are administrator on local machine, ASP.Net development server will run under elevated administrator privileges.
2. Reduced features: ASP.Net Development server is a trimmed down version of IIS and does not support all features. For e.g. you cannot use, Server.Transfer in ASP.Net development server.

So a local IIS is the best option for developing web applications locally on developers machine as it closely mimics the live environment.

Comments

Richard Byrdk said…
This comment has been removed by the author.
21 December 2012 at 13:32
Post a Comment

Popular posts from this blog

Searching Unicode characters in Oracle table

Oracle implementation of Regular expression has no support for using hexadecimal code to search for Unicode characters. The only way to search for Unicode character is it use the character itself. Normally with Regular expression, you can use \x or \u followed by hexadecimal code to search for any character. E.g. \x20 will match space. But REGEXP_LIKE in Oracle does not support \x. You need to use unistr function to convert the code to equivalent character and then use it with REGEXP_LIKE. E.g. REGEXP_LIKE(source,'[' ||unistr('\0020')|| ']');
Post a Comment
Read more

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0
Post a Comment
Read more

How to get started with .Net Core and Lambda functions?

 Recently I started experimenting with .Net Core and AWS Lambda functions, I thought I will share the steps I took to get started Tools to install .Net Core 3.1 -  https://dotnet.microsoft.com/download/dotnet-core/3.1 AWS CLI -  https://aws.amazon.com/cli/   AWS Account - 12 months Free Tier -  https://aws.amazon.com/free Terminal - on iOS I use iTerm2 -  https://www.iterm2.com   Once you installed the above tools, head to AWS console and login with your root account to create an account which will be used by AWS CLI. Please see steps here   Now you can configure AWS CLI as detailed here . Verify that you able to connect to AWS service using CLI. To make life little easy with dotnet core and Lambda functions, you need to install AWS Extensions nuget pack for .Net CLI dotnet tool install -g Amazon.Lambda.Tools You can also install templates to get started quickly  dotnet new -i Amazon.Lambda.Templates That's it. Now the fun part!!!  Creat...
Post a Comment
Read more