Re: Limiting folders that get published to the web server
- From: daveh551 <geekdh@xxxxxxxxx>
- Date: Mon, 28 Jul 2008 07:00:08 -0700 (PDT)
On Jul 28, 12:09 am, stch...@xxxxxxxxxxxxxxxxxxxx (Steven Cheng
[MSFT]) wrote:
Hi Brian,
From your description, you're wondering how to limit the folder or pages in
ASP.NET web application which will be published. Is the "publish" here
means the "publish Website" in Visual studio?
If this is the case, I think the publish website behavior is abit hard to
customize(such as apply for only some certain folders or page). This is
because "publish website" is not simply move pages or folders from your
local development location to product server. It does the following things:
1. perform a precompilation for your web application( generate precompiled
assembies) so that your application will avoid some startup dynamic
compilation at runtime.
2. Move all the precompilation output and the original page stuffs to server
So for precompilation, it may precompile some pages or folders together
into the same assemblies, therefore, the pages or folders cannot be
separated (someone not to precompile) here for the entire process.
If your application do not need precompilation and can be directly deployed
via the page files and source code files, you can use the "copy website"
function to synchronize the application content to the target server. In
Visual studio, you can use "copy web site" from the following menu:
"website--->copy web site..."
you can connect to a certain server/application virutal dir and synchronize
files betwen it and your local web application.
If you have anything unclear, please feel free to let me know.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer tohttp://msdn.microsoft.com/subscriptions/managednewsgroups/default.asp...
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) athttp://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Thread-Topic: Limiting folders that get published to the web server
thread-index: AcjubhppBx1/qS9lQm6KlD55yVSDcA==
From: =?Utf-8?B?QnJpYW4=?= <bkbroi...@xxxxxxxxxxxxxxxx>
Subject: Limiting folders that get published to the web server
Date: Fri, 25 Jul 2008 08:50:03 -0700
I have a web site project that has many folders and files, as I knowothers
do as well. When I make changes to the site it usually only affects a few
files.
Is there a way to limit what gets published to only the files that were
changed, added, or removed?
--
Brian
From my limited experience with VS 2005 (about 3 months), I wouilddescribe it just a little differently.
When I click "Publish Website" in the Build menu, it does do the pre-
compilation that Steven described, but it puts the results in a folder
called "Precompiled Web" in my projects directory, ready to be copied/
FTPd to my host.
Also, if you check "Allow the site to be updatable" and don't check
"Use fixed naming and single-page assemblies", then it will include
the full text of your aspx files as distinct files in the precompiled
version. It will still compile ALL your code-behind pages into one
dll, but if you don't ever open a particular page (or include it in
the download), then those code-behinds will never be called. (My
understanding - I don't usually do it, so I haven't verified this - is
that if you uncheck "Allow site to be updatable", then your aspx file
is effectively rolled into the code-behind page, and hence, the dll,
and then the aspx file that is copied just becomes a placeholder
invoking the code-behind file.
Anyway, if you do all that, then you can choose what to copy from the
"PreCompiled Web: folder to your hosting site.
Like I say, that's just my limited experience, and I hope it helps.
.
- References:
- RE: Limiting folders that get published to the web server
- From: Steven Cheng [MSFT]
- RE: Limiting folders that get published to the web server
- Prev by Date: RE: Limiting folders that get published to the web server
- Next by Date: What happened to Global.asax?
- Previous by thread: RE: Limiting folders that get published to the web server
- Next by thread: RE: Limiting folders that get published to the web server
- Index(es):
Relevant Pages
|
