Problem after upgrade with ASP.NET subsites seeing root web.config and not their own

Original configuration:

ASP application for the root web site
Subsite applications were various ASP.NET (1.1 and 2.0) sites with their own web.config
Subsite applications were access using www.domain.com/app1

After upgrade:

Root web site became a ASP.NET site with it's own web.config
Subsite applications break because they only see the root web.config

What is the best way to remedy this and have subsite application still access using www.domain.com/app1?

Using Windows Server 2003 Standard and IIS6.

Thanks!
OCSDTechAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
samtran0331Commented:
So the root web site after the upgrade is still Classic ASP right?
I'm not sure you can "remove" ASP.Net from it...but since it isn't an ASP.Net site, you could try removing the root's web.config (just rename it to something else)...and see what happens...
0
 
OCSDTechAuthor Commented:
The root web site after the upgrade is now ASP.NET and it needs to be ASP.NET as certain features are based on .NET.
0
 
samtran0331Commented:
Coincidentally, this question was right before yours...see the link I posted in the solution...
http://www.experts-exchange.com/Programming/Languages/.NET/ASP.NET/Q_24385966.html?cid=236#a24317800
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
OCSDTechAuthor Commented:
samtran0331,

The root site has three subsites: 2 running 2.0.50727 and 1 running 1.1.4322.

The 2.0.50727 subsites and the root site work fine but the 1.1.4322 subsite complained about the xmlns of the <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> statement.

When I took that part out, the 2.0.50727 subsites and the root site still worked but the 1.1.4322 subsite now complained about the inheritInChildApplications attribute in the location element.
Parser Error Message: Unrecognized attribute 'inheritInChildApplications'.

The 1.1.4322 subsite doesn't like the new 2.0.50727 attributes.
0
 
samtran0331Commented:
Is the 1.1x app still actively being developed?
If not, in IIS switch the ASP.Net version for that app from 1.1x to 2.x
I've had situations where a 1.1x project will work fine under the 2.x framework...and I've had other situations where it just completely blows up.  You might have to make some minor web.config changes... But if you can get it to run under 2.0, the inheritInChildApplications attribute will work.

If the 1.1x project is still actively developed/changed...I would recommend you upgrade the project to 2.0...it will take a little effort but I've never had a failed upgrade.

Alternately, you might just have to run the 1.1x app in a separate web site...you could redirect any users that use the old address to the new address...but I don't know if there is any other way around this "child app" problem...
0
 
OCSDTechAuthor Commented:
samtran0331,

I should have mentioned it in our last post but I did try having the 1.1x subsite run under 2.x and the subsite ran okay except that the Crystal reporting stopped working under 2.x.  

As you suggested, we're now looking into upgrading the project to 2.x.  Hopefully that will be relatively painless.
0
 
samtran0331Commented:
The upgrade would be the best route any way you look at it.

But you said:
subsite ran okay except that the Crystal reporting stopped working under 2.x.  

One thing you might want to try is:
1. create a new 2005 asp.net 2.0 project.
2. Add a crystal report to it and look at the web.config entries for crystal.
3. see if putting/replacing those entries in the old app's web.config makes the old app run under 2.x

Good luck!

0
 
OCSDTechAuthor Commented:
Thanks for all your help.  It looks like we'll be looking to update the 1.1x site to 2.x.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.