Gap asp.net web application

Question

Looking at gathering some opinions on how to split a web application (or perhaps a set of web applications) (by project) ... basically, it will all be one big site, but the problem arises from the fact that it has many modules, each of which has its own dev / release loops.

The problem is that splitting them becomes a headache, trying to make sessions collaborative between sites and embedding shared resources in a DLL, but keeping them as one big project is a nightmare from the point of view of the source.

Possible ways to do this that I can think of:

• You have one application and a branch, like crazy to work on each module:. In a fundamental style, this seems right, but there would be many branches and merging branches all the time would be a nightmare ...
• Make all the separate applications: The disadvantage is that they all share their master pages and many user controls (implemented in ascx). I know how to put them in a DLL (using virtual path providers), but this is a pretty dirty solution. In addition, it is the transfer of the session back and forth between applications, mainly creating a solution for a homegrown session ...

Another thing that I tried to figure out if I can do but fail is to somehow create a "virtual folder" in csproj so that, for example, the folder "ModuleA" actually displays on "../../ ../ModuleA/Trunk/ ". I am sure this cannot be done without using any pre-build scripts, but I was hoping for something that would really load in Visual Studio, so I think this idea does not work ...

Does anyone have any tips on how I should go about this (be it one of the above or something that I haven't considered)? Want to make sure that I don’t shoot a foot here, because it is rather a long-term project with a lot of future improvements / services ...

Answer 1

I did this in one of our projects. There is a certain specific problem that we encountered during development, but it is definitely worth highlighting the project in a separate dll for ease of maintenance

As you also suggested for the virtual path provider, I have a specific link for the same that might help you. Also, to transfer data between two modules, we created properties in the interface and created a separate project for the interface, and all modules implement this interface, so we can transfer values ​​from one module to another.

In addition, it is always advisable if you are creating a modular application, then it should be independent of the other, but ultimately it depends on your requirements.

Link1

UC from the database

Specific links for sharing sessions between applications (I would not suggest sharing a session, but still, if you want you to be able to view these articles)

ASP.Net Forum

Using State Server

fooobar.com/questions/860514 / ...

Answer 2

If you are building a project, I'm not sure that it is a good idea to use asp.net 2.0 because of the problems you have. At some point in my project, I moved these ascx controls to separate the “control library project”, which simply gets me the html lines, which are then placed somewhere on the site. Like the syntax <% = fControl%> inside aspx pages that I populate with this code. Not an elegant solution, but made much simpler. In any case, we decided to redefine the project in php, since it is cheaper and does not create such problems.