Powered by Blogger.

Saturday, March 1, 2014

Packaging and deployment of asp.net application

ASP.Net contains a lot of pieces that are all possible parts of the overall application and need to be deployed with the application in order for it to run properly. The following list details some of items that are potentially part of your asp.net application and need deployment consideration when you are moving your application.

Also you can check out:

- Singleton class in C#.Net

- How to get Column names of table in SQL Server 2008?

- Export Data Of DataGridview To Excel using C# Windows Appllication

- .aspx pages
- The code-behind pages for the .aspx pages(.aspx.vb or .aspx.cs files)
- User controls.
- Web service files(.asmx and .wsdl files)
- .htm or html files.
- Image files such as .jpg or .gif.
- ASP.NET system folders such as App_code and App_Themes.
- JavaScript files(.js).
- Cascading Style Sheets(.css)
- Configuration files such as the web.config file.
- .Net components and compiled assemblies
- Data files such as .mdb files.

Before deploying your ASP.NET web applications, you should take some basic steps to ensure that your application is ready for deployment. These steps are often forgotten and are mentioned here to remind you of how you can ensure that your deployed application performs at its best.

The first step you should take is to turn off debugging in the web.config file.



    <compilation debug="false"/>



The second step is to build your application in Release mode.You can accomplish this by changing the active solution configuration from Debug to Release through the drop down list
in the visual studio menu.