FAQs in the category: Model.Category
On the right you find the list of faqs published on this Web site in the category VS 2005 conveniently split up in pages.
If you can't find what you're looking for, try another category from the sub menu
| Details |
 |
|
| Site Section | FAQs | |
| Site Section | VS 2005 | |
| Number of
items |
1 | |
| Last Article Added |
2/29/2004 5:36 PM |
Now reading
Below you find some of the books that I am currently reading.
-
Inferno by Dan Brown
-
Implementing Domain-Driven Design by Vaughn Vernon
-
Pro ASP.NET MVC 4 by Adam Freeman
-
Search Engine Optimization (SEO): An Hour a Day by Jennifer Grappone / Gradiva Couzin
How Do I Precompile an ASP.NET Whidbey Application?
UPDATE (2005-12-06): The compilation features presented in this article are obsolete. It's recommended that you look at Web Deployment Projects (http://weblogs.asp.net/scottgu/archive/2005/11/10/430283.aspx) instead.
Unlike Web sites created with Visual Studio .NET 2002 or 2003, there is no need to do a full compile of the project whenever something has changed in your site. The new Code Behind feature and the Code directory used in ASP.NET Whidbey allow you to make changes without recompiling. As soon as the changed page gets requested, the .NET FRamework will recompile the page on the fly.
However, it is sometimes useful to compile the application right after you have deployed it. One reason for this precompilation is speed. Another is code protection. A compiled application does not expose its source in the ASPX pages any longer. There are two ways to compile an application at deployment time: In-place compilation and Precompilation for Deployment