Home/ Questions/Q 3694070
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T04:27:10+00:00

I know why this happens and I want to find a workaround it. Example:

  • 0

I know why this happens and I want to find a workaround it.

Example: a user control that exist in 2 assemblies, loaded at the same time.

namespace MyNamespace
{
    internal class MyUserControl : UserControl
    {
    }
}

My situation – I want to be able to share user interface control between two web applications which are loaded at the same time in the same application pool. If my user interface class is marked public, then ASP.NET will not like it because it will be duplicated into memory ( CLR uses namespaces as full qualifier for class, and if the same class and namespace is met it more than one assembly, exception is thrown ). I do then mark the class as internal and of course I forget how UI compilation occurs, and I expect it to work. Of course it doesn’t because ASP.NET compiles the UI into separate assembly which is dynamic and since I marked the class as internal, it is not visible to the main assembly…

The question that follows is: How can I make dynamic compiled assemblies that ASP.NET generates to view the main application assembly internals? It is very unfortunate that classes and methods I write into my UI controls must always be public! Has anyone met this obstacle in his daily work and found a workaround?

EDIT:

Precompilation is not possible here due to other circumstances.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can share User Control markup between apps using a Virtual Path Provider (see
    http://weblogs.asp.net/scottgu/archive/2005/11/27/431650.aspx and http://msdn.microsoft.com/en-us/library/system.web.hosting.virtualpathprovider.aspx).

    You can pull the markup for the control from anywhere – SharePoint uses VPP to get markup from the database, and I use it in some projects to pull from a non-standard location on disk (which is shared between projects).

    • 0