I think you'll find out that fails, Bruce.
I tested that scenario, extensively, and failed every time.
As soon as the subvdir encounters a non-version specific web.config setting: crash!
However, maybe my tests were not as complete as I think they were.
If you can produce proof-of-concept, I'll acquiesce.
Juan T. Llibre, asp.net MVP
aspnetfaq.com :
http://www.aspnetfaq.com/
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
===================================
"Bruce Barker" <br******************@safeco.com> wrote in message
news:Oa**************@TK2MSFTNGP15.phx.gbl...
make a seperate dir for the 2.0 stuff (as it needs to be its own vdir anyway), that is in a
differnt path. when you create the vdir, just make the 2.0 vdir under the 1.10
ex:
c:\sites\version1\mysite1
c:\sites\version2\mysite2
in iis create vdir one
path c:\sites\version1\mysite1
alias: /mysite1
in iis create vdir one
path c:\sites\version2\mysite2
alias: /mysite1/mysite2
-- bruce (sqlwork.com)
"Robert" <Ro****@discussions.microsoft.com> wrote in message
news:0E**********************************@microsof t.com...I am trying to run ASP.Net 2.0 pages within a ASP.Net 1.1 application. The
2.0 pages are located in a sub-directory of the 1.1 application. Once I
create a new web.config file in the 2.0 folder the 1.1 applcation fails. I
cannot set up a second application for the 2.0 pages due to sharing
application and IIS settings.
I have a couple of questions -
1) How should I access the data in the 2.0 web.config file without breaking
the 1.1 application? Should I create an external reference in the 1.1
web.config and rename the 2.0 web.config?
2) I am using the Enterprise Library, how do I tell the Enterprise Library
to reference a file other than the web.config file?
Thanks