I must admit I was mistaken.
I just reproduced your structure ( a 1.1 app running under a 2.0 app )
and have found that, indeed, the 1.1 app balks at 2.0-only web.config
configuration entries in the 2.0's app's web.config.
Now, I realize that we may have been trying to ignore Application boundaries.
An Application is defined as all the files in a subdirectory which has
been marked as an Application...and all the files in all subdirectories
of the Application's root.
Anything which is included under the application's subdirectory *must* run under
that application's "rules", and apparently that includes the target .Net Framework.
Testing further, I found that after I created the VS 2003 project and closed it,
I couldn't open it again, getting an "http 500 internal error" message.
Moreover, the 1.1 app ran OK...as long as I didn't assign it to a 1.1 AppPool.
As soon as I assigned it to a 1.1 AppPool, that caused an "Application Unavailable"
error message in all my 2.0 apps, which can only mean that it's running under 2.0 rules,
even though the ASP.NET tab is marked as targeting the 1.1 Framework.
Bottom line : you can't mix .Net Frameworks within the same application.
Sorry. I wish I had better news for you.
Juan T. Llibre
ASP.NET MVP
ASPNETFAQ.COM :
http://www.aspnetfaq.com
==================================
"Patrick Teas" <pa************@nospam.com> wrote in message
news:%2*****************@TK2MSFTNGP14.phx.gbl...
Hi.
I'm having the exact same problem as Nate.
My Virtual Directory has an application name, MyAppName, with a starting point that is <Default
Web Site>\MyAppName.
I have removed the application name and re-created, yet it still has a starting point under
<Default Web Site>.
I need the url for the 1.1 site to be remain under the 2.0 site like it is now.
So how do I get my virtual directory to behave like an application of it's own, yet still be
accessed at the url http://myTopLevel2.0Site/my1.1site?
Thanks for the help.
Patrick Teas
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:%2***************@TK2MSFTNGP15.phx.gbl... re: Why does the 1.1 application care what is in the web.config file of the 2.0
application? Is there some further way to seperate the two?
You need to understand the difference between a Virtual Directory and an Application.
A Virtual Directory will inherit from the Application which it's a Virtual Directory of.
It makes sense that 2.0 web.config settings create problems for a 1.1 App.
An Application stands alone and does not inherit from any other Application.
Try making your 1.1 Virtual Directory an Application.
You might need to implement session-sharing between them
if you are using session state for critical application data.
Juan T. Llibre
ASP.NET MVP
ASPNETFAQ.COM : http://www.aspnetfaq.com
==================================
"Nate" <co*******@noemail.noemail> wrote in message
news:55**********************************@microsof t.com... Your understanding of my situation is not correct. My site is layed out like
the diagram below.
Web Sites
--ABC Site (built in and configured to use 2.0.xxxx in App Pool 1)
----A Virtual Directory (built and configured to use 1.1.xxxx in App Pool 2)
When the virtual directoy application built in 1.1 starts it throws a parse
error if there are any nodes in the web.config file of the ABC Site 2.0 site
that are specific to ASP.NET 2.0 (e.g. <connectionStrings/> or <urlMappings
enabled="true">).
I have tried running the 1.1 application under 2.0 but it does not work.
Why does the 1.1 application care what is in the web.config file of the 2.0
application? Is there some further way to seperate the two?
