Geek Answers Handbook

Best practice for multiple asp.net web applications

Look for best practice if you have multiple web applications on the same ASP.NET website or “solution”. I have several options that I play with:

  • old faithful translation of all applications and site master into one solution / one web application

  • My boss is concerned that 30 “applications” that are under the same project in VS, and every time we make changes to one, need to be deployed for everyone. Thus, it makes us want to break up each individual project under the same solution. This makes us look at master page solutions.

    • The main page should support a dynamic menu structure. Is this something I can do with one SiteMaster? Is VirtualProvider solution right for this? Does anyone have any good tutorials?

  • Creating a UserControl for each application and a link to it in the main application

+3
source share
2 answers

1) Thus, it makes us want to split each into a separate project under the same solution.

(A good idea)

The master page should support a dynamic menu structure.

As a note, have you ever heard of MEF ?
It is very convenient for your business.
Using it, you can have a complete, extensible solution to the main page with the ability to add additional menus (and functionality for everyone) on the fly !!!.
MEF technology, you can have a separate project under a single solution. Each (new / updated) project can be

  • Published / Reprinted.
  • merge content files with the main already published site (master project)
  • Copy the generated dll of the child project to the bin folder
  • Reload the site.

Here are a few articles about it: Microsoft Link , CodeProject Basics for ASP.Net
There is also a concept called Portable Area . But I don’t know how it works or what kind of script it covers, or even if it is applicable to Asp.Net or only to Asp.Mvc . just try it if you want.

+1
source

I asked two similar questions:

Cross project master page

The best bet is individual projects within the same solution and using the Nuget package to synchronize common artifacts, including master pages. Now it works great in the 22 design decisions I'm working on. You can also save the Nuget package itself in the original control.

Update:

You can use the XML file for your menu and share it with Nuget. It is possible to add jQuery for the sliding effect, etc.

+3
source

More articles:


All Articles