Hi Mike,
As for the problem you mentioned, I have performed some research in our
internal case records and did found some former cases with the similar
problem. Here are some possible scenarios that will occur such problem:
1) When we publish the website with the ¡°updateable¡± check OFF and then
copy some
files on deployment location that has some markup or code in them. By
putting the
¡°updateable¡± check OFF we instruct the asp.net compiler to compile all
the markup
and code into dll files so that further on asp.net would not consider
runtime
compilation of content. But if it needs to (due to the presence of such
content) it
will throw that error.
2) The second situation is when we have a web application configured in
VS.Net to
run directly off IIS (the http project) and then we publish it to the same
location
again with the ¡°updateable¡° checked OFF. There will be development files
at same
location which will cause similar errors.
3) Another situation is where we have a precompiled website and within the
root
folder of it we have another folder that has content for another asp.net
application but isn¡¯t marked as application in IIS. ASP.Net tracks asp.net
applications when running on IIS by virtual directories in IIS marked as
applications. A child folder having un-compiled content within a parent
application
which is precompiled will again cause this error.
So far I've found the following workarounds and solutions according to the
above cases:
Giving the target location for Publishing as a local folder and then
copying the contents to the actual IIS machine. We created a mapped drive
for the remote location on the development machine and gave this drive as
the
target location in the Publish dialog. We had the "Updateable" check ON but
the "Fixed Naming check OFF.
Since this problem is not quite easy to troubleshoot the root cause, if you
still get error after try the above approahes, I suggest you contact CSS
for further troubleshooting.
http://msdn.microsoft.com/subscriptions/support/default.aspx
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.
