"Michael Schwarz" <no****@schwarz-interactive.dewrote in message
news:ek***************@TK2MSFTNGP02.phx.gbl...
"Mark Rae" <ma**@markNOSPAMrae.comschrieb im Newsbeitrag
news:et**************@TK2MSFTNGP03.phx.gbl...
>"Michael Schwarz" <no****@schwarz-interactive.dewrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
>>>>It will always be the root folder of your web application. With Visual
Studio internal web server it will be always a sub folder. ASP.NET
will set the correct path automatically.
So why is it not...?
[...]
>>How do you include the WebResource.axd?
What do you mean by how do *I* include it...*I* don't do anything - it
just happens as part of ASP.NET 2, does it not...?
yes, but where is the problem, is the path there wrong?
Michael,
The problem is as I outlined in the original post - I obviously haven't
explained it clearly enough...
On the development workstation running WinXPPro, the web application resides
within a virtual directory called intranet. When the web application is
running on the development workstation, the path to WebResource.axd as shown
in View Source is <script src="/intranet/WebResource.axd..."- this is
correct, works.
On the production server running Win2ks3, the web application is deployed in
its own site, not a virtual directory as such. When the web application is
running on the development environment, the path to WebResource.axd as
showin in View Source is *also* <script
src="/intranet/WebResource.axd..."- this is not correct, and does not
work - it should be <script src="/WebResource.axd...">
Two things make the web application work on the production server:
1) to create a subfolder called intranet in the web site and deploy all of
the files into that
2) to deploy the site into a virtual directory
There is obviously something somewhere which is telling ASP.NET to create
the WebResource.axd file in a subfolder called intranet...
Mark
