I have the same problem with my own project. I am using MasterPage thru
Web.Config <Pages masterPageFile= "~/MasterPage.mast er">. Once I compile,
and deploy, project does not run beyond VS.NET. It can not load the Master
file itself, let alone other resources. The error for MainApp is
"The file '/MainAppPCW/MasterPage.mast er does not exist'
I get this error only beyond development environment. Just note that I have
tried so many different way to compile and deploy, looked all around for help
on Virtual Directories, paths, virtual paths. Could not find anything. How
is that possible? This is a standard out of the book and out of the samples
configuration I am using. Someone related to Whidbey team should reply to
this at the earliest.
"Wernfried Schwenkner" wrote:
I have compiled the portal sample comming whit whidby. While running it
ftom the IDE it works, all buttons on the start page are shown.
When I deploy the portal with the Menu "WebSite/Publish", the login,
download and create new account button isn't shown. A compare of the
html source code shows the reason:
On the published version a "PCW" is appended to the web name (I assume
it measn pre compiled web).
<img src="/PortalPCW/Themes/White/Images/button-download.gif"
alt="download photo" style="border-width:0px;" />
But the directory doesn't have this name, it is without the "PCW".
How can I prevent this?
--
Sleepless in Berlin
W. Schwenkner