E
EO
I'm using an ISP with poor tech support. I apologize if this is more of an
ISP question, but it is an asp.net question as well.
I have a root domain pointing to a root level folder. There are several
folders in this root domain, each of which are aliased to other domain
names.
I used Visual Studio, through FP Extensions, logging in through the root
level domain name to create a web application in a new directory, then
published an application to it, again, publishing to a subfolder of the root
domain. I then pointed a second domain name to use that folder as its home
directory.
I then disabled frontpage extensions, because they have other nasty
implications with this isp.
Now, if I browse to http: // rootdomain/appfolder/default.aspx, the world
is happy.
But if I browse to http: // appdomainname/, I get "could not load type
appName.default"
I've also tried having the isp create an application folder without fp
extensions on (Can't do that myself). Same results.
Whassup?
ISP question, but it is an asp.net question as well.
I have a root domain pointing to a root level folder. There are several
folders in this root domain, each of which are aliased to other domain
names.
I used Visual Studio, through FP Extensions, logging in through the root
level domain name to create a web application in a new directory, then
published an application to it, again, publishing to a subfolder of the root
domain. I then pointed a second domain name to use that folder as its home
directory.
I then disabled frontpage extensions, because they have other nasty
implications with this isp.
Now, if I browse to http: // rootdomain/appfolder/default.aspx, the world
is happy.
But if I browse to http: // appdomainname/, I get "could not load type
appName.default"
I've also tried having the isp create an application folder without fp
extensions on (Can't do that myself). Same results.
Whassup?