Hello Zany,
As for the ASP.NET 2.0 web project's precompilation and publishing, we will
need to take care of the following things:
1. If you're precompiling web site as updatable, the aspx,ascx template
file's content will be preserved and other codebehind and component classes
will be precompiled into assemblies(output in bin directory). Also, you'll
find that the @Page or @Control directive in aspx/ascx template will
reference new class (in precompiled assemblies). Therefore, after such
precompilation, we'd better update all the files to the target deployment
location so that all the changes are updated.
2. If you're precompiling the website as non-updatable, the content of
aspx,ascx template is also removed and those files become a placeholder(no
application data in it). In such cases, since the aspx and ascx files are
just placeholders, you can avoid redeploy them to target location(as long
as they're ready there), however, you still have to update all the newly
generated assemblies and any other deployment necessary files(like the
xxxx.compiled file) to the target deployment site's "bin" directory also.
For detailed information about ASP.NET 2.0 website's precompilation model
and how the files are processed during precompilation, you can refer to the
following MSDN document:
#ASP.NET Web Site Precompilation
http://msdn2.microsoft.com/en-us/library/ms228015.aspx
Also, for Web Deployment project specific featuers you can refer to the
following article. IMO, web deployment project mainly focus on some
additional customization options when performing precompilation(such as
assembly naming...):
#Using Web Deployment Projects with Visual Studio 2005
http://msdn.microsoft.com/library/en-us/dnaspp/html/web_deployment_projects.
asp?frame=true
Please feel free to let me know if you have anything unclear or any other
questions.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
