ASP.NET: Versioning the Same Website

Question

My new job assignment is to create a second version of our existing web application. Currently, our application supports only full-term brokers, but now we are launching a second site specifically for time brokers.

The new site will be almost identical to our existing site with the following exceptions:

• He will have his own branding.
• The pair of user controls used to display the information will be different (but none of the pages will be different).
• Our existing users should not have access to the new site and vice versa.
• It is easy to test both versions of a website from Visual Studio.
• We want to make the most of our existing code.
• I have 2 weeks to do this.

I hope this is a common scenario, and someone has advice on how to do this.

Answer 1

I really, really do not recommend branching projects or other routes that involve copying what is essentially identical to the code, with the exception of branding and authorization. In the end, of course, it will be easier, but, as you said, it will become a nightmare very quickly, trying to keep almost the same code bases.

, , , , . . , . , , , , .

, , () .

, - , .

Answer 2

, . , , , . ?

Answer 3

• - IIS.
• script ( -)
• usercontrols
• ( )

Visual Studio , .

Control Version... .

, , ... , , ..

Answer 4

While I really like the idea of ​​CaptainTom, another solution is to break the display layer of your application from the rest of the logic and create a new project that implements a new user interface, as well as use the rest of the code

i.e. the FillTimeBrokers project and the PartTimeBrokers project, which implements its logic from the general Brokers project.