Projection Plan #2: Publishing a Complete ASP.NET Project
At this time I’m assuming you have moved your sensitive information to App_GlobalResource. This step talks about publishing your project rather than keeping all separate files.
By that I mean, converting your entire website into web executable rather than leaving all logic open for anyone to see.
By converting your project into “published" project, visual studio.net strip out all of the code from your asp.net classes and your pages, and convert them to .dll files. Which as we know are not human readable. See the screen shot below which shows which icon to click.
Once you start the publishing process, you will have to enter a new path for the published code, which you can FTP to your hosting company.
Once you follow plan #1 and plan #2 above, you will be sure to protect your sensitive information such as SQL database connections strings and username / password. Also you will be able to project your business logic from anyone who has access to your hosting folder.
You might think you trust your hosting person or company, but in reality you are giving them the information which can bring your website down.
It’s better to be safe than sorry.