Here's about VWD:
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=859b1375-3c9c-41c1-a1ae-b54081bc1519
You can do precompilation for deployment manually with VWD by using aspnet_compiler.exe (it is part of the Framework)
Here's about using it
Usage:
aspnet_compiler [-?] [-m metabasePath | -v virtualPath [-p physicalDir]]
[[-u] [-f] [-d] targetDir] [-c] [-fixednames]
[-keyfile file | -keycontainer container [-aptca] [-delaySign]]
-? Prints this help text.
-m The full IIS metabase path of the application. This switch
cannot be combined with the -v or -p switches.
-v The virtual path of the application to be compiled (e.g.
"/MyApp"). If -p is specified, the physical path is used to
locate the application. Otherwise, the IIS metabase is used, and
the application is assumed to be in the default site (under
"/LM/W3SVC/1/Root"). This switch cannot be combined with the -m
switch.
-p The physical path of the application to be compiled. If -p is
missing, the IIS metabase is used to locate the app. This switch
must be combined with -v.
-u If specified, the precompiled application is updatable.
-f Overwrites the target directory if it already exists. Existing
contents are lost.
-d If specified, the debug information is emitted during
compilation.
targetDir The physical path to which the application is compiled. If not
specified, the application is precompiled in-place.
-c If specified, the precompiled application is fully rebuilt. Any
previously compiled components will be re-compiled. This option
is always enabled when targetDir is specified.
-keyfile The physical path to the strong name key file.
-keycontainer Specifies a strong name key container.
-aptca If specified, the strong-name assembly will allow partially
trusted callers.
-delaysign If specified, the assembly is not fully signed when created.
-fixednames If specified, the compiled assemblies will be given fixed names.
-nologo Suppress compiler copyright message.
Examples:
The following two commands are equivalent, and rely on the IIS metabase. The
compiled application is deployed to c:\MyTarget:
aspnet_compiler -m /LM/W3SVC/1/Root/MyApp c:\MyTarget
aspnet_compiler -v /MyApp c:\MyTarget
The following command compiles the application /MyApp in-place. The effect is
that no more compilations will be needed when HTTP requests are sent to it:
aspnet_compiler -v /MyApp
The following command does *not* rely on the IIS metabase, as it explicitly
specifies the physical source directory of the application:
aspnet_compiler -v /MyApp -p c:\myapp c:\MyTarget
With Visual Studio 2005 you have Publish Website feature which allows you to deploy the app to a site (either with aspx updates allowed like in v1 or totally non-updateable). It has the same features as using aspnet_compiler (it's just bundled into the tool)
Thanks,
Teemu Keiski
Finland, EU