If you don't have an /app_code directory, or only have a few files defined within it, the page designer will be able to load much quicker (since it doesn't need to perform a big compilation first).3) Enable the on-demand compilation option for your web-site projects.
To learn more about VS 2005 Web Application Projects, please review the tutorials I've published on my
Note that VS 2005 Web Application Project support will be included in VS 2005 SP1 (so no additional download will be required going forward).
Use the techniques outlined in this blog post to fix it.
2) Keep the number of files in your /app_code directory small.
What this means (when you select the "Build Page" option in the dialog above) is that when you edit a page and then hit F5 (run with debugging) or Ctrl-F5 (run without debugging) the solution will compile all of the class library projects like before, then compile the /app_code directory and file, and then instead of re-verifying all pages within the web-site it will only verify the current page you are working on, and any user controls that the page references.
With large (and even medium) projects with lots of pages, this can obviously lead to major performance wins. NET will automatically re-compile any other page or control you access at runtime -- so you will always have an up-to-date and current running application (you don't need to worry about old code running).Both the VS 2005 Web Site Project option and the VS 2005 Web Application Project option will continue to be going forward with future Visual Studio releases.What we've found is that some people love one option, while disliking the other, and vice-versa.Quick Background on VS 2005 Web Site Project and VS 2005 Web Application Project options VS 2005 supports two project-model options: VS 2005 Web Site Projects and VS 2005 Web Application Projects.VS 2005 Web Site Projects were built-in with the initial VS 2005 release, and provide a project-less based model for doing web development that uses that same dynamic compilation system that ASP. VS 2005 Web Application Projects were released as a fully supported download earlier this spring, and provide a project model that uses a MSBuild based build system that compiles all code in a project into a single assembly (similar to VS 2003 -- but without many of the limitations that VS 2003 web projects had with regard to Front Page Server Extensions, IIS dependencies, and other issues).From a feature perspective there is no "one best option" to use - it really depends on your personal preferences and team dynamics as to which will work best for you.