Databases
StackOverflow2013
Postsdbo
POSingle Codebase multiple websites
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSingle Codebase multiple websites
    primarykey
    data
    text
    <p>We have developed a system that uses a single code base, consisting of four Visual Studio projects with an admin website, and customer facing website (each system has its own MS SQL database).</p> <p>This has been working great, as all new websites (including admin) reference the same code base projects from within SVN, therefore any changes made to the code base are then available to all websites.</p> <p>Each website has a different master page, and different user controls (.ascx), and therefore partially different although the main coding behind the sites is the same.</p> <p>The issue we are having now is if there is a bug, a feature change or a new feature we have to implement it in ALL the sites separately (for both admin and customer site). Which is starting to drive us insane, and also means we have a HUGE margin of error for implementing the changes.</p> <p>I have thought about using svn:externals but this will become messy.</p> <p>Branching from a master website and master admin system could be the option, but merging to get the new code is a major issue with the sites not being exactly the same.</p> <p>I think a nice overview would be say that the markup is totally different per site (except the admin site, which is just a theme change) but the code bases are the same.</p> <p>What is the best way to manage this or are we stuck doing a lot of copy and paste?</p> <h2>EDIT</h2> <p>Which points would you like clarity on?</p> <p>Issues that arise are such as in page JavaScript being different, HTML layouts can be completely different bewtween websites. But the code for the pages is the same.</p> <p>So I would need to 'synchronise' file and folder such as those found in app_code, but there are issues here as well.</p> <p>Site 1 and Site 2 could be exactly the same, just a different theme. Site 3 has a different theme as well, but it also has some bespoke code that is only required by this site, some of the code in app_code also acts differently to Site 1 and Site 2</p> <p>Now I could easily achieve this with branching, but when merging up to the new branches, if there are code differences then there are going to be major conflicts.</p> <p>Merging would also become a large task and take too long, as we would need to merge only certain folders and files, although you cannot merge a single file through the branch (this could be wrong).</p> <p>For example:</p> <p>In the root there is a download.aspx which returns a stream as the response rather than a page, this is used to push all the download requests through the system.</p> <p>So this page in Site 1 and Site 2 is the same, but in Site 3 it does something extra which no other site requires or needs.</p> <p>We don't want this bespoke feature to be an overload as we don't want/need it for the other websites, we can now no longer merge this file, from the master website, it must be manually merged.</p> <p>Hope this explains better what I am trying to achieve.</p> <h2>EDIT 2</h2> <p>Basic site structure</p> <pre><code>|- App_code |- App_Themes |- Bin |- Content | |- Flash | |- Images | |- Scripts | |- Uploaded | |- Controls | |- MasterPage | | |-MasterPageControls | | | |- Navigation | |- Search | |- Templates | | |- Control Templates | | |- Page Templates | | | |- WebServices | |- Errors | </code></pre> <p>Everything under Controls Navigation, Search, Templates is .ascx files.</p> <p>In the root there are several files including default.aspx, download.aspx and preview.aspx</p> <p>These are the main pages for the website (ignoring Error pages), all pages are dynamically created from the DB.</p> <p>The Controls folder is where most of the changes between websites happens in the MasterPage, and all other user controls.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJamesStuddart
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSingle Codebase multiple websites
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSingle Codebase multiple websites
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSingle Codebase multiple websites
      1. USleonm
      1. VTFavorite
    1. COInteresting to see if Jeff Atwood chimes in on how they manage this exact problem with stackoverflow, I'm not aware that it's been talked about anywhere before.
      singulars
      1. POSingle Codebase multiple websites
      1. USDominic Rodger
    2. COCould the original poster please try to clarify and edit for brevity?
      singulars
      1. POSingle Codebase multiple websites
      1. UScsl
    3. COThis is a great question
      singulars
      1. POSingle Codebase multiple websites
      1. USblu
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload