T
Tessa
Hi,
For an existing asp.net 2.0 web site which is not on the default web site,
or uses a different port number, what is the syntax to precomplie using
aspnet_compiler?
e.g. aspnet_complier -v "/myvirtualdirectory" works if my web site is at
http://servername/myvirtualdirectory
but what do you do if your as.net web app is at
http://servername:7654/myvirtualdirectory ?
We've got 2 websites on 1 server which are differentiated by the port
number.
I keep getting errors like : error ASPRUNTIME: '/:7654/myvirtualdirectory'
is not a valid virtual path
I've also tried using the -p syntax e.g. aspnet_compiler -v
"myvirtualdirectory" -p "c:\inetpub\wwwroot2\myphysicaldirectory" but this
doesn't work either - it's just as slow as ever on first hit.
Do you have to resort to getting the exact details from the IIS metabase
first and specifying that using -m ?
What do you do also if you have a web app that is on the default website but
not on port 80?
any help much appreciated
Tessa
For an existing asp.net 2.0 web site which is not on the default web site,
or uses a different port number, what is the syntax to precomplie using
aspnet_compiler?
e.g. aspnet_complier -v "/myvirtualdirectory" works if my web site is at
http://servername/myvirtualdirectory
but what do you do if your as.net web app is at
http://servername:7654/myvirtualdirectory ?
We've got 2 websites on 1 server which are differentiated by the port
number.
I keep getting errors like : error ASPRUNTIME: '/:7654/myvirtualdirectory'
is not a valid virtual path
I've also tried using the -p syntax e.g. aspnet_compiler -v
"myvirtualdirectory" -p "c:\inetpub\wwwroot2\myphysicaldirectory" but this
doesn't work either - it's just as slow as ever on first hit.
Do you have to resort to getting the exact details from the IIS metabase
first and specifying that using -m ?
What do you do also if you have a web app that is on the default website but
not on port 80?
any help much appreciated
Tessa