Developing modern applications in cloud

Solution (sln) file. Solution user Options (.suo) file. Project configuration file (.vbproj) or .vcproj file .aspx, .asmx, .ascx .aspx.vb or .aspx.cs - code behind fiels globax.asax resouce file .resx other files .txt, .rpt style .css files congig file web.config. discovery file .disco or .vbdisco Project Assembly files (.dll)—All of the code-behind files (.aspx.vb and .aspx.cs) in a project are compiled into a single assembly file that is stored as ProjectName.dll. This project assembly file is placed in the /bin directory of the Web application. AssemblyInfo.vb or AssemblyInfo.vb or AssemblyInfo.cs—The AssemblyInfo file is used to write the general information, specifically assembly version and assembly attributes, about the assembly.

There are several conditions that will cause an application domain to shut down and restart. When ASP.NET must restart an AppDomain, it simply removes the entry in the table that points to the AppDomain. When a new request arrives, the table does not have an entry; therefore, ASP.NET creates a new AppDomain that handles all of the future requests. The old AppDomain continues running until it completes all of its current requests. Finally, the old AppDomain shuts down. The following changes will cause an AppDomain to restart: Configuration change—If the machine.config or Web.config files are changed, ASP.NET detects the change and restarts the affected AppDomain. Global.asax change—If the global.asax file is changed, ASP.NET detects the change and restarts the affected AppDomain. Bin directory change—If an assembly in the bin directory is changed, ASP.NET restarts the AppDomain that corresponds to that bin directory. Compilation count change—When an ASP.NET Web page is changed, it is re