Secret ingredients to quality software

Do you avoid deploying source code on the production server?

Last updated by Tiago Araújo [SSW] on 12 Mar 2021 10:56 pm (5 months ago) See History

When you are deploying an ASP.NET project (no matter it's a Web site or a Web application), do not copy all files of this project to the production server because source code will be deployed during this simple copy and it makes easier for others to access or tamper the source code of your site.

Instead, please use 'Publish' utility to deploy your Web site or Web application. This utility can remove the source code from the site.

1. Web Site Project

Publish Web Site dialog box is designed to precompile and deploy your Web site to a new location (whatever it is, ftp://, http:// or drive:\path). During the deployment, source code are removed automatically. Besides, the precompilation process finds any compilation errors and identifies the errors in the configuration file.

To access this dialog box, please open a Web site that you want to deploy and click Build menu, then click Publish Web Site .

Figure: How to open Publish Web Site dialog box

Figure: Publish Web Site dialog box

See more about Publishing Web Sites.

2. Web Application Project

The Publish Web dialog box enables you to build and publish a Web application project to a new location. Like Publish Web Site dialog box, this utility can remove source code. However you have to select Only files needed to run this application to specify it. Other benefit of this utility is that potential errors and compile-time errors in the Web.config file and in other non-code files can be found.

To access this dialog box, open a Web application project that you want to publish and click Publish ApplicationName on the Build menu.

Figure: How to open Publish Web dialog ('WebApp' is the name of this application)

Figure: Publish Web dialog box

See more about How to Publish Web Applications.

Adam CoganAdam Cogan

We open source. This page is on GitHub