January 3, 2018 at 10:19 am
We use Team Foundation Server (TFS) on-premise, here at work. We've got some source code for a third party app that we use, that's vital to our business. It is older however, but that's another story. There's also a SSIS package, which I didn't even think we had the source code for. One of my colleagues did find the source code, again older, but at least we have something. However, instead of putting it into TFVC (TFS's source control) she put it into TFS's SharePoint Portal view. (The Shared Documents folder.)
So, OK, this sorta works. When I went looking for the SSIS package I didn't think to look in the TFS SharePoint Portal, but that more or less means its in source control. However, I'm wondering if it wouldn't be better to put it into TFVC instead?
We're using SQL Server 2008 R2 SP2.
Kindest Regards, Rod Connect with me on LinkedIn.
January 3, 2018 at 11:04 am
I've put SSIS packages in TFS source control for years, so I know it works. My opinion is that it probably makes the most sense to keep it in source control as opposed to the SharePoint documents folder. While SharePoint does provide some simple versioning, it would seem best to keep all your source in one place, and TFS would be the more robust option. It's about fitness to purpose, and using the tools for what they were designed for. SharePoint is more of a content management system for end users, while TFS is a development and testing suite of tools.
January 3, 2018 at 1:44 pm
Yes 100% put it into Source control.
Just don't expect to be able to have 2 people work on the same package and then merge changes. Due to the xml format the merge conflicts will be a nightmare and trying to merge changes would most likely result in a corrupt file.
January 4, 2018 at 8:01 am
FridayNightGiant - Wednesday, January 3, 2018 1:44 PMYes 100% put it into Source control.
Just don't expect to be able to have 2 people work on the same package and then merge changes. Due to the xml format the merge conflicts will be a nightmare and trying to merge changes would most likely result in a corrupt file.
That is very good to know. Too bad that it isn't possible for 2 or more people to work on it at the same time. Guess, in a sense, its the nature of the beast (SSIS).
Thanks.
Kindest Regards, Rod Connect with me on LinkedIn.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply