Home/ Questions/Q 162313
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T11:22:07+00:00

This question is a follow up to my question about sharing resources between web

  • 0

This question is a follow up to my question about sharing resources between web applications, because I have not yet found a good solution.

I have a web application with user controls and resources that are shared by three other web applications.

 Solution | +-CommonControlsWebApp | +- resources | |  +- images | |  +- scripts | |  +- stylesheets | +- UserControls |  +-WebApp1 |  +-WebApp2 |  +-WebApp3

This is what I know this far:

  • I can not compile CommonControlsWebApp into a single dll since I am creating user controls. This is only possible with custom server controls, where everything is in the code-behind file. So I need a way to share the ascx files between the four projects.
  • Copying the files from CommonControlsWebApp into the three other projects does not update their files in the solution explorer. I would have to ‘add exting items’ all in all three WebApps when a file is added or renamed in CommonControls.
  • Changing to the Web Site model would remedy this, but I am worried about the compile time for WebApp1-3 if I do this.
  • ‘Add as link’ does not work for directories.
  • I could use Subversion to share the files between the projects, but i believe that this would require me to check the files in and out again all the time if I am developing a user control that I have to test through one of the WebApps.

Can it really be true that ASP.NET does not have a good solution for this? How are you guys organizing large web applications?

Edit: Thanks a lot for all the answers. I am going to copy my user controls with a build event for now, and then see if we have time to refactor them into server controls.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. The way we do it at my present company is to make sure CommonControlsWebApp is a WebApplication, not a web site. Then you use names for the folders that would help identify it as the common ones that are distinct from the individual web apps. (CommonUserControls instead of just UserControls)

    In your other web apps, you create a virtual directory to the CommonUserControls, etc, and add a file based reference to the CommonControlsWebApp.dll

    This requires you to use IIS for development (not casini), and Visual Studio won’t believe that the controls really exist, but it will work at runtime, and you can build just fine with only warnings about blahblah.ascx or blahblah.master path invalid.

    If you do use common master pages and Visual Studio 2008, you will need SP1 for 2008 and use a __fallback.master in the root of the individual web projects to go in to design mode.

    However, I saw this on another thread, and I am going to look into doing more like this: http://webproject.scottgu.com/CSharp/UserControls/UserControls.aspx

    • 0