Geeks With Blogs

News Ashraful Alam Joy

Create Your Badge

Ashraful Alam is a Software Architect, who has 8 years of professional experience in Software Development industry. This Bangladeshi national is involved with project management and development of several US based software projects from his country. Already he has managed and developed several software projects, which are being used by several users of different countries, such as USA, Canada, Australia, and Bangladesh. While developing and managing a team, he contains and maintains a set of well defined engineering practices developed by him and other online developer communities.

Due to his willingness to give effort to improve and share better software development practices, Ashraf has been awarded as “Most Valuable Professional” (MVP) in ASP.NET category by Microsoft since year 2007 multiple times, which is a rare honor and prestigious reorganization among the developers around the world.

Check his portfolio to know more about him and his works.

.NETTER Characters... Every part of your life is best, if you can know yourself and thus create your life like an artist!

Deploying an ASP.NET 2.0 is a bit tricky than before. Specially if you are habituated to work in ASP.NET 1.x application for previous few years you will be really confused to see how you should deploy your ASP.NET 2.0 application that you just built.

Well unlike previous cases, VS.NET 2005 doesn’t generate any assembly by default in the web application “bin” folder for each built. When you build an application, it shows the output on the fly. However when you finish your coding and development, and decide to deploy this project in web server, you need to right click on the web project icon in the solution explorer, and have to choose “Publish Web Site” item from the context menu. In the provide window you have to set the location where the project output should be copied which can be a ftp, http, local IIS folder or a physical hard drive path. You have three check box, where you will set the deployment behavior.

1. Allow this precompiled site to be updatable

With VS.NET 2005, you can deploy a site with out having any html content in the aspx file, where the contents will be embedded in the compiled dll and complied extension included file, although you have to place the blank aspx files in the remote server as a place holder. Really exiting isn’t it? You don’t have to copy the changed aspx file to the remote server, and thus just copy the relevant dll into the server, no matter how many pages have been changed. In that case you have to uncheck this option. Other wise html contents will be available in the aspx file in the deploying application output.

2. Used fixed name and single page assemblies

If you check this option, separate assemblies will be generated for each pages, otherwise not. It may be a good thing to work, specially form our country where the internet bandwidth is pretty low, and it consumes much time to deploy a dll of a large web application.

3. Enable strong naming on precompiled assemblies

Which enables strong naming on precompiled assemblies.

Important Note: For minimum set of deployment files for traditional web application in bin folder atleast 5 files will be generated.
App_Web_tnasqyo2.dll – the main dll that holds the content.
App_global.asax.dll, App_global.asax.compiled – will be generated when there is global.ascx in the project.
App_Code.dll, App_Code.compiled – will be generated when there is codes in “App_Code” project folder.
Posted on Saturday, July 8, 2006 2:49 PM Implementation , .NET , Software Development | Back to top

Comments on this post: VS 2005 Project Deployment Issues

# re: VS 2005 Project Deployment Issues
Requesting Gravatar...
hi good work
Left by sheeji on Oct 15, 2008 12:25 PM

Your comment:
 (will show your gravatar)

Copyright © Ashraf Alam | Powered by: