RE: Limiting folders that get published to the web server
- From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng [MSFT])
- Date: Thu, 31 Jul 2008 10:05:33 GMT
Hi Brian,
How are you doing?
Have you got any progress on this issue or does the information in previous
message help some? If there is anything else need help, please feel free to
post here.
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:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng [MSFT])
Organization: Microsoft
Date: Mon, 28 Jul 2008 05:09:29 GMT
Subject: RE: Limiting folders that get published to the web server
in
Hi Brian,
From your description, you're wondering how to limit the folder or pages
ASP.NET web application which will be published. Is the "publish" hereserver
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
deployed
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
via the page files and source code files, you can use the "copy website"synchronize
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
files betwen it and your local web application.f
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:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#noti
ications.
.
- 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: Why is My Default Page Code Executing
- Next by Date: RE: Limiting folders that get published to the web server
- 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
|