Creating/accessing an application directory

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?
 
E

EO

Issue solved, answer provided for the curious:
For reasons known only to gurus & gods, it is necessary to put the
project.dll in the bin folder in both the application directory AND a bin
folder off the root directory. Ditto for replicating the web.config file.
Add that and it's golden. You won't likely see that in any textbook, so just
in case anyone shares my bizarre experience, that's the solution.
 
J

Jeffrey Palermo [MCP]

EO,
Does the appfolder have the bin directory in it? Is it configured as an
application? Both of these have to be true for your appdomainname to work.
Just a regular subfolder won't work. It has to be configured as a separate
web application.

Best regards,
Jeffrey Palermo
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top