 troyh78
|
| Joined: 15 Jan 2009 |
| Total Posts: 2 |
| |
|
SSAS Best practice for multiple developers / what to save in code repository?
Posted: 15 Jan 2009 02:44 PM |
We are moving from a single developer to three developers potentially working at the same time on our Analysis Services solution created in Microsoft Visual Studio. This has raised the question of what files we should be saving in our code repository (we're currently using CVS for other no Visual Studio projects) to basically ensure we don't lose anything, and can revert to previous versions if need be.
Q1. What files should we be storing into the repository to ensure we can revert back to previous versions if need be? Here's what the project folder for this solution looks like:
D:\MyProject\MyProject
D:\MyProject\MyProject.sln
D:\MyProject\MyProject\bin
D:\MyProject\MyProject\obj
D:\MyProject\MyProject\Account.dim
D:\MyProject\MyProject\Forecast Versions.dim
D:\MyProject\MyProject\General Ledger Group.dim
D:\MyProject\MyProject\General Ledger Type.dim
D:\MyProject\MyProject\AnalytxDSV.dsv
D:\MyProject\MyProject\AnalytxDS.ds
D:\MyProject\MyProject\PromaxAnalytx.cube
D:\MyProject\MyProject\PromaxAnalytx.partitions
D:\MyProject\MyProject\MyProject.database
D:\MyProject\MyProject\MyProject.dwproj
D:\MyProject\MyProject\MyProject.dwproj.user
D:\MyProject\MyProject\SKU HIERARCHY.dim
D:\MyProject\MyProject\Time.dim
D:\MyProject\MyProject\bin\MyProject Script 20081209.xmla
D:\MyProject\MyProject\bin\MyProject Script 20081212.xmla
D:\MyProject\MyProject\bin\MyProject Script.xmla
D:\MyProject\MyProject\bin\MyProject.asdatabase
D:\MyProject\MyProject\bin\MyProject.configsettings
D:\MyProject\MyProject\bin\MyProject.deploymentoptions
D:\MyProject\MyProject\bin\MyProject.deploymenttargets
D:\MyProject\MyProject\obj\Development
D:\MyProject\MyProject\obj\Development\LastBuilt.xml
D:\MyProject\MyProject\obj\Development\IncrementalShapshot.xml
Q2. What happens when checking code back into the repository when a conflict is detected? I am assuming that if we are checking in the xml looking files like the dimension files Forecast Versions.dim and Time.dim that we will be able to use a program like WinMerge to step through the conflict and make changes as required?
I would appreciate any advice but comments from developers who are in the same situation and already have a working method would be very much appreciated. |
|
|
 |
|