01 Nov 2012
13 Sep 2013
Link to this post
Myself and the other developer both simply replicated a production setup on our development machines:
- Source code in the C:\inetpub\wwwroot directory
- IIS with an appool for each site, and a website that points to that directory
- MS SQL Server with a database for each site (running locally), pointed to by the dataconfig.config file
- Edit files in visual studio, build in visual studio, and then load the page in the browser.
We use git for version control, and for all code changes to staging and production, the code is pulled and built. Configuration files are excluded from version control so that we don't overwrite settings that were changes by users in production (and so that the database references don't get overwritten with dev settings). All custom modules and database changes are replicated by hand for production sites.
It's a bit of a pain, but it works pretty well.