Sharing App_Code between different web Applications

Hey,

We have a very large ASP and ASP.NET Application.  The application is predominently ASP but new parts of it are being developed in .NET.  In the application there are ASP security pages stored in /system/security which are included in every ASP page.  When we first moved over to .NET we re-wrote the various security pages into various VB.NET security classes which are inherited onto each .NET page, ensuring that security is applicable to both ASP pages and ASP.NET pages.  This all works fine.

The problem arises that although there is one big application, there are also smaller applications inside it.  In IIS there is a main website that links to the root of the application.  There are also other websites that link to directories inside the application such as: /subapplications/subapp1/.  These sub applications have virtual directories  that link to the /system/security directory of the main application (so we can still use the security from the main application).

The problem is that we are now starting to write .NET pages in our sub applications.  We started by creating a virtual directory in the sub application IIS website called App_Code, which (we thought) would enable this IIS website to see our classes.  However we were just given this error message:  

The path '/App_Code/' maps to a directory outside this application, which is not supported.

Further investigation shows that maybe we need to set the sub application to use the AppDomain of the larger application, but we haven't really pushed this.

We are aware of the DLL route, but would like to avoid this if possible.  However suggestions of this type would be appreciated.  We also understand that the two applications should not be nested, however at this moment in time, it is imperative that they are.

Many thanks for the help
LVL 1
ukwebguyAsked:
Who is Participating?
 
samtran0331Commented:
>>The path '/App_Code/' maps to a directory outside this application, which is not supported.

I don't think you'll get around this, "App_Code" is a special folder that the Framework recognizes and handles a specific way.

>>We are aware of the DLL route, but would like to avoid this if possible.

In my opinion, the DLL route is ideal, why are you trying to avoid it?
If your solution in Visual Studio was set up:
-MainSolution
---SharedCode (Class application)
---Website1
---Website2
---WebsiteEtc

SharedCode would be a class application that inherits from system.web (which would give you access to everything to everything in the web namespace)
And all your websites reference SharedCode.
When you compile/publish, the DLL will get dropped in each website's \bin.

This is (in my opinion) the ideal way to share code...and other routes will probably cause more problems that it solves...
0
 
mrichmonCommented:
All ASP.NET folders App_Code, App_Data, etc are special folders that have different permissions and restrictions than normal folders.  They are specifically treated as outside of the application so that you can have things like your database located in your App_Data folder and know it is safe from external browsing.

You have two choices for shared code.

One is the dll - I agree with samtran0331 that this is not a bad way to go at all.

Another is to expose anything you need as a web service - which is probably more hassle than you want.
0
 
ukwebguyAuthor Commented:
Thanks guys,

We suspected that this would be the only real solution.  I think we were trying to use classic ASP techniques in an ASP.NET environment.

Thanks guys.
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.