I have a site with many application roots below the main root
- mainSite (application root)
- subfolder2 (application root)
I have a database connection saved in my database explorer that when test, does work. I created a Linq to SQL in the subfolder2 application and the connection string is saved in /subfolder2/web.config. This works absolutely perfectly.
Today I attempted to go in and create the admin page (as part of the primary root, but in a folder) for this newest subfolder application - like I have done a million times. First I create the empty Linq to Sql object, everything continues to work. But as soon as I add the table for the new application to the dbml, everything dies. First I get the Custom Error screen telling me to turn off custom errors, and when I do, I get the blank 500 server error on EVERY page, including html and css files, and not just in the root application, but in the nested applications as well.
First, what on Earth could possibly be so bad that IIS stops serving html files?
Second, why would the dbml editor allow me to add the table if there is something wrong with it?
Third, why is this functioning in other applications? Is it some sort of duplicate nested information issue for either t
View Complete Post