Publish Failed

[GaryDean]

although my publish usually works for my asp.net 2.0 projects, sometimes it
just says "Publish Failed". Is there anywhere I can look to see the reason?
Perhaps a log?

--
Regards,
Gary Blakely

[Dave]

On Jan 30, 4:38 pm, "GaryDean" <GaryD...@newsg roups.nospamwro te:

although my publish usually works for my asp.net 2.0 projects, sometimes it
just says "Publish Failed". Is there anywhere I can look to see the reason?
Perhaps a log?

--
Regards,
Gary Blakely

The output window. View -other windows Output window

[Steven Cheng[MSFT]]

Hi Gary,

As Dave has suggested, the straight info about website publishing is the
output window. Generally the publish web site will go through the following
two steps:

1. perform precompilation against the web application

2.clear the target directory(virtu al directory in IIS or physical file
folder) and deploy all the files (of the web application) into the target
directory

In the output window you can check at which stage does the publish website
operation fail. For example, at the first stage, if there are some error
which will only occur at precompilation, that will cause the stage 1 fail.
Or some times if the target directory has something configured incorrectly.
Such as the IIS virtual dir is not set to the correct ASP.NET version or
some old files are locked and prevent them from being cleared. Mostly,
publish failed will be caused by IIS side configuration issue such as
authenitcation setting....

So far there is no dedicated log file on this at VS 2005 side.

If there is any further questions on this, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

=============== =============== =============== =====

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.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/subscripti...t/default.aspx.

=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.