I am posting a message I found in the forums from months ago that went unanswered - I am experiencing the same problem - I have virtual directories that require .NET 1.1, like SQL Reporting services and some upload forms - but I want my main website to be DNN 4 on .NET 2.0

A solution or workaround would be greatly appreciated!  

Josi.

"We spent the last several months migrating our aging site, which was written in classic ASP, to DotNetNuke and have finally decided to go live with our new DotNetNuke site, however, we ran into an issue in doing this.  And I was wondering if someone on the forums could help.  We have one IIS website hosting several ASP.NET 1.1 applications.  So DotNetNuke is at www.example.com, and the applications are at www.example.com/an_application/, www.example.com/another_application, etc.  We do not want to change the location of these apps because we have lots of clients using them.  The problem that we are running into is that the .NET 1.1 apps are reading DotNetNuke's web.config and erroring out on .NET 2.0 specific settings like requirePermission="false".  After googling for a bit, I was able to find a page explaining how to get .NET 1.1 to ignore certain sections from a .NET 2.0 web.config, unfortunately this solution will not work with DotNetNuke because DotNetNuke uses a <sectionGroup> which AFAIK there is no way to tell .NET 1.1 to ignore.  Does anyone know how we can get this to work?"

You should be able to have the following configuration.

1 website for the DNN site with ASP.NET 2.0

Then craete virtual directories for each sub site, but be sure that you have an application name speciried.  (Under Home Directory ensure that the application name is not greyed out)

Doing this sets the "Starting point" for the application and allows you to run multiples in the same website.