February 24, 2015 at 6:57 am
Hello,
Looking for some multi developer/report best practices.
We have hundreds of student system reports and three report developers.
Should we have one student system solution file (stored on a network drive), a shared data source within that solution and multiple projects/report (rdl) within it?
Are there any issues with multiple developers accessing/saving within the same solution/project? Locking errors?
Or should we have one solution/project per report? But then we lose the shared data source.
Any other thoughts?
Thanks
Jim
February 24, 2015 at 7:15 am
Do yourself a favour and use proper version control tools.
Popular version control systems:
* Git
* Mercurial
* SVN
* CVS
* TFS
See here for a quick comparison: http://www.sitepoint.com/version-control-software-2014-what-options/
Visual Studio can work with all of the above.
-- Gianluca Sartori
February 26, 2015 at 3:10 pm
We have 6 developers on the database team. We use TFS for source control.
In TFS, we keep only the .rdl files, not projects. The developer working on it checks it out, makes changes, and checks it back in. If another developer needs to make changes, they will see that the other one has it checked out and will coordinate changes with them.
We each have our own projects and manage them however it works best for us.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply