*sigh* Stephen ur just saying the same thing over and over, which doesn't work for me. A Visual Studio project folder that has a subfolder with a web.config that has conflicting settings will always yield the error I mentioned. I'm looking for another way to organize my projects/ solutions so that it won't error.
Anyone else? Sammael? On Sep 2, 9:26 am, Stephen Russell <[email protected]> wrote: > On Wed, Sep 1, 2010 at 4:32 PM, Buddy Z <[email protected]> wrote: > > Nope, debug mode doesn't make a difference Stephen. Still get "This > > error can be caused by a virtual directory not being configured as an > > application in IIS." for my local environment. Still works fine on the > > server. > > > The answer probably has to do with best practices in Visual Studio, > > when setting up a website where the root web.config and a subfolder's > > web.config have conflicting settings. It's not an issue when you have > > IIS, because you can designate both the root folder and subfolder as > > applications. But what do I do on my local computer (non-IIS) in > > Visual Studio to avoid the above error? > > > Still waiting for someone knowledgeable about Solution/Project setup > > to chime in here... > > ----------------------------- > > I do WCF programming all the time. I then have to put a GUI up to > interact with my service. On my dev box I don't run the WCF in an IIS > space just in ASP.Net Development Server space. I think that you have > to do the same thing to READ your web.config file in the SUB app and > yet run the primary app as well. > > -- > Stephen Russell > > Sr. Production Systems Programmer > CIMSgts > > 901.246-0159 cell
