How do you deploy and manage a C # web application for a client with some minor differences from your base project?

I have a semi-large web application that we run locally and I need to deploy it elsewhere. Second place will require minor changes in the design (especially cosmetic ones). How do you manage these differences and what do you use to distribute the site and updates for such a client?

Edit: Our web application is now running internally and we are building using Cruise Control.NET and MSBuild with WDP. What would be a good deployment option for the client? We will not update their site for them, so it is advisable that they be easy to deploy and update.

+5
source share
4 answers

Paste your code.

I hope your code is controlled by the source code (if not, start now!), You should go from the base to the "Customer X" branch and just make small cosmetic changes in this branch. Then just create and expand this branch for this client.

In addition, if the changes are small enough, you can try to change the settings. Thus, you can deploy the same site everywhere and just change the configuration to suit what the client wants. The more complex the differences, the more difficult it will be to set them up.

: , , , # , . ( )

: β†’ ( ), β†’ ( ).

+12

. . :

  • : db
  • : , css,
  • :
  • :

. , .

+2

, . - ; "" .

"" .

+1

Custom fixes are a pain for this reason. Usually we just connect to our original control system and manually apply the changes after the update using a script. Due to the additional overhead, we cancel user patches as much as possible.

0
source

All Articles