February 3, 2016 at 4:41 pm
We have several different versions of SSIS, installed mostly long ago on servers alongside a particular db version (MSSQL 2005, 2008, 2012 and 2014). So for SSIS changes, we've been logging into the test servers, and using older versions of Visual Studio and SSIS when maintaining these projects.
I'm working under the assumption that I can't just upgrade these SSIS projects using VS2012, and expect them to run under the SSIS environment running on these older servers.
I'd like to get all of these into TFS though. I have some experience with SVN from a prior job, and this is where the following question comes from ....
Is there something like Tortoise SVN, but for TFS, so that I can check projects out of TFS directly onto the file system, then, log into the test server for development, then when I'm done, return to Windows Explorer to check things back in? That way, I can retain the SSIS versioning on the source code. I guess it's possible I could possibly check projects in and out with VS2012 - without developing in that environment, but then I'm concerned that someone might inadvertently work on the item, thus upgrading it and then being forced to revert back and start the changes over again.
I keep finding references to TFS Source Control Explorer, but I can't tell if it's a stand-alone tool, or integrated into Visual Studio.
Or maybe someone else has an idea of how to develop in this varied environment, using TFS?
--=Chuck
February 3, 2016 at 8:22 pm
TFS integration with Visual Studio varies between versions of Visual Studio. The later versions (I think either from Vs2012 or VS2010), TFS explorer was available out of the box. For earlier version, you needed to install the TFS explorer.
Either way, once you have VS talking to TFS, changing a file that is under source code control is detected. What happens next is really dependent on your TFS/VS configuration.
February 3, 2016 at 9:26 pm
chuck.forbes (2/3/2016)
We have several different versions of SSIS, installed mostly long ago on servers alongside a particular db version (MSSQL 2005, 2008, 2012 and 2014). So for SSIS changes, we've been logging into the test servers, and using older versions of Visual Studio and SSIS when maintaining these projects.I'm working under the assumption that I can't just upgrade these SSIS projects using VS2012, and expect them to run under the SSIS environment running on these older servers.
I'd like to get all of these into TFS though. I have some experience with SVN from a prior job, and this is where the following question comes from ....
Is there something like Tortoise SVN, but for TFS, so that I can check projects out of TFS directly onto the file system, then, log into the test server for development, then when I'm done, return to Windows Explorer to check things back in? That way, I can retain the SSIS versioning on the source code. I guess it's possible I could possibly check projects in and out with VS2012 - without developing in that environment, but then I'm concerned that someone might inadvertently work on the item, thus upgrading it and then being forced to revert back and start the changes over again.
I keep finding references to TFS Source Control Explorer, but I can't tell if it's a stand-alone tool, or integrated into Visual Studio.
Or maybe someone else has an idea of how to develop in this varied environment, using TFS?
--=Chuck
For managing SSIS you'll want to get SQL Server Data Tools (SSDT) which is a brand name for "Visual Studio (VS) plus Project Types for SQL Server Database Projects, SSIS, SSRS and SSAS Project Types." It's free and if you do not already have VS installed it will install the VS Shell (bare bones free version).
As for connecting to TFS I do not think Team Explorer is bundled with SSDT (in cases where you do not already have VS and get the VS Shell from the SSDT installer) but you can get it here:
Team Explorer for Microsoft Visual Studio 2012
If you already have VS 2012 Professional then you should already have Team Explorer. Look for the Team Menu. Team Explorer is basically the client for TFS, i.e. like Tortoise for SVN, and it too relies on the existence of VS. Team Explorer is installed as an Add-in for VS.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
February 4, 2016 at 6:06 am
Have a look at TFS Power Tools.
You'll need to select the correct version for your environment. Once you've done that, you'll get a certain amount of TFS functionality available to you straight from Windows Explorer – maybe it will be of some help to you.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply