I see clearer now.
As I recall SharePoint requires Windows Server 2003 so just create another
website for your other application(s) which will have its own root separate
and distinct from SharePoint.
<%= Clinton Gallagher
<co*********@gmail.comwrote in message
news:11**********************@d34g2000cwd.googlegr oups.com...
I have not touched the machine.config file. Should I?
If I place the test web.config file under inetpub\wwwroot my test
application works fine. However I need this location for sharepoints
web.config file.
Cheers
clintonG wrote:
I'm taking a wild guess until somebody else with SharePoint experience may
comment but ask what you have done to inspect the machine.config file?
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP 43°2'17"N 88°2'37"W : 43°2'17"N 88°2'37"W
<co*********@gmail.comwrote in message
news:11*********************@m73g2000cwd.googlegro ups.com...
I've a test web site set up as a virtual directory under default web
sites in IIS. However when I browse to the main .aspx page I get an
error because it is referencing a web.config that belongs to sharepoint
web sites. How can I force the test web site to reference the correct
web.config file?
The test web site contains the following in IIS:
Default Web Site
Test - contains aspx and web.config
Bin
The test web site virtual directory points to a folder on the D drive
e.g d:/TestWebSite which holds the web.config
The error references a web.config on d:\inetpub\wwwroot\web.config. How
can I force the test web site to look at the correct web.config file
The Test Web site virtual directory uses a different application pool
to sharepoint and has been excluded from the sharepoing virtual server.
I'd appreciate any help
