What is the difference between developing ASP. net programs on Windows azure and Windows Sever?

[Original] the differences between development on Windows azure and Windows Server

Summary

Azure architecture and status management

For architecture considerations, common ASP. NET applications are no different from those on azure. Some important aspects include:

• WholeProgramSuch as N-layer service-oriented (n-tier or SOA ),CodeWhere does the job exist and run.
• Define the service and user-oriented layers ).
• Where is the data stored.
• Status management and performance.
• Security.

If you want to migrate ASP. NET applications running on IIS to Azure, refer Azure Application Profile Guidance[PDF].

Status management is a tough issue that ASP. NET developers often face, especially when considering performance and scalability. For more information about the cache mechanism on Azure, see Differences between caching on-premise and azure caching. For ASP. NET page output cache, you can use output cache provider for Windows azure. If session is used, session State provider for Windows azure can be used on azure. The ASP. net provider architecture makes it easy to migrate applications to azure. For more information about cache, see Windows azure caching services.

Differences between tools and projects

For ASP. NET web forms and ASP. net mvc developers, there is no big difference in development tools. For details, refer to get started with the Windows azure tools. Install the Windows azure SDK for. Net, which includesWindows azure tools for Visual Studio. Use it during local development Windows azure developer emulator to run your program, instead of vs built-inSp. NET development web server or IIS Express.

ASP. NET Applications on azure are generally divided into two types: Web role and worker role. vs includes these two types of project templates. The Azure Project template is actually a standard ASP. NET web forms or ASP. net mvc project.Microsoft. Windows azure and other related namespaces. The. config configuration file contains the configurations required to be deployed on azure.

deployment, diagnostics, instrumentation, monitoring, quality of service, and uptime (ensure normal service time) For more information, see the original article.