Yes, we have been running with the Sitefinity folder added to source control as well, Visual Studio 2008 - integrated mode. We're quite new to Sitefinity, but we did look close at the options when making our own "best practices" for the project soruce control and
Sitefinity upgrade cycle.
I just have a few minor comments/questions, for assurance during Sitefinity upgrades late at night, when trying to overwrite, merge and leave alone the correct amount of files...
Sorry, I might be a bit off topic here, driving at both upgrades and versioning.
I guess/hope merge jobs are rare, I just want to be prepared.
For example, I modified the files files SearchBox.ascx and searchCommonLayout.css in the folder ~/Sitefinity/ControlTemplates/Search/. At the same time I assume that most controls will be altered a bit during upgrades, and files need to be modified to accommodate additional functionality.
We can cope with a few merge jobs now and then, but I would really appreciate a simple way of checking which files might need a merge. For instance, the two mentioned files were not not altered from v3.7 to 3.7SP1. But I had to check (using WinMerge) as these files in the 3.7SP1 patch archive were had more recent date than the v3.7 patch.
Could incremental patches be an idea? Anyway, a list of changed files would be great, covering files int he Sitefinity folder and similar locations that potentially could be modified by the developer.
Moving on, we considered input from the post Installing Sitefinity as a Web Application in Visual Studio
We have avoided the WebSite project types all the way (meaning this is a bit unfamiliar), but still we decided to stick with the current Sitefinity upgrade path as I read somewhere that you might consider a WebApp version somewhere from Sitefinity 4.0.
So, we need to cope with WebSite projects unable to exclude files using the integrated source control connector. The bin folder is fortunately left alone from source control, but everything else seems to get absorbed. The exclude from project option would rename files and is useless in this context as far as I can see. We just have to remember to check out certain files before doing certain operations using the Sitefinity browser based site management at the development computer:
- Adding pages, if an index is set to update automatically (writes to files in ~/App_Data/Search/ )
- Uploading controls, (would write to web.config). But we had to take that one manually anyway.
Anybody know of more project file writing operations that we should be aware of?
Comments are very much appreciated! Thanks!