Recent Articles

AMicrosoft Bridging VB6 And .NET Forms
A new toolkit from Microsoft will allow VisualBasic 6 developers to craft .Net WinForms that can be displayed in a VB6 application.

ASP.NET: How To Create Custom Trace Messages
This article is an excerpt from the book: Murach's ASP.NET 2.0 Web Programming with C# 2005.

How To Use Breakpoints
This article is an excerpt from the book: Murach's ASP.NET 2.0 Web Programming with C# 2005.

How To Use The Exception Assistant
This article is an excerpt from the book: Murach's ASP.NET 2.0 Web Programming with C# 2005.

ASP.NET: Testing a file-system web site with IIS
This article is an excerpt from the book: Murach's ASP.NET 2.0 Web Programming with C# 2005.

10.13.06


Visual Studio 2005 - Publishing Web Site

By Kenny Tran

What's the purpose of site precompilation? As it turns out, improved performance is often brought as an evidence of the benefits of precompilation.

While precompilation certainly saves users from the notorious first-hit delay, I don't believe that this simple fact, which affects only one user per page, is going to change users' feelings about the overall usability of the site.

Precompilation is mostly a safety measure: using precompilation makes your application safer because when you deploy it you know that all pages compile without errors. In addition, your precompiled application is safer because any valuable source code is out of reach.

To get both benefits you must opt for deploy precompilation. This form of precompilation creates a read-only image of the site that might be packaged to MSI or ZIP files as well as directly x-copied to the web server machine.

Managed Hosting Solutions Powered By Rackspace

For web sites that are subject to frequent page updates, updateable deploy precompilation is probably better because updateable precompilation allows you to edit and add new pages. These new pages will be compiled on first hit, though.

If you leave the Allow this precompiled site to be updatable checkbox checked, markup inside of your Webforms and user controls will not be pre-compiled into a DLL allowing you to make changes after deployment. If you would prefer to lock down the markup so that changes to the deployed content are not allowed, uncheck this box.

The Use fixed naming and single page assemblies checkbox allows you to disable batch compilation so that each page is compiled into a fixed-named assembly. Leaving this box unchecked allows you to take advantage of batch compilation.

The Enable strong naming on precompiled assemblies checkbox allows you to strong-name your precompiled assemblies.

Note: In ASP.NET 1.X, strong-named assemblies had to be installed into the Global Assembly Cache (GAC). In ASP.NET 2.0, you are not required to install strong-named assemblies into the GAC


About the Author:
Kenny Tran is the author of the "Kenny and .NET" blog.

About WebProASP
WebProASP is a collection of up to date tutorials and insightful articles designed to help ASP users of any skill level implement successful ASP systems and practices. ASP Strategies and Tactics for Business

WebProASP is brought to you by:

SecurityConfig.com NetworkingFiles.com
NetworkNewz.com WebProASP.com
DatabaseProNews.com SQlProNews.com
ITcertificationNews.com SysAdminNews.com
WebProASP.com WirelessProNews.com
CProgrammingTrends.com ITManagementNews.com




-- WebProAsp is an iEntry, Inc. publication --
iEntry, Inc. 2549 Richmond Rd. Lexington KY, 40509
2006 iEntry, Inc.  All Rights Reserved  Privacy Policy  Legal

archives | advertising info | news headlines | free newsletters | comments/feedback | submit article



ASP Strategies and Tactics for Business WebProASP News Archives About Us Feedback WebProASP Home Page About Article Archive News Downloads WebProWorld Forums Jayde iEntry Advertise Contact