Vault v10.0.1 and DTS 2017

[dsalter]

We have recently upgraded to Vault 10 in order to support DTS 2017. We have one person who is using DTS 2017 and installed the Vault_VisualStudioExtension_10.1.793/vsix and is encountering a couple of issues:

#1: When opening any solution from Vault, even checked out, he the message:

The source control provider associated with this solution could not be found. The projects will be treated as not under source control.

Do you want to permanently remove the source control bindings from the projects?

#2: Only the Solution in DTS shows checked in or out, with a lock or check mark.
The dtsx packages do not show any icons. This is only an issue with DTS 2017, not our older SSIS 2008.

[jclausius]

Can you provide a list of the tools involved? For example, what tools are involved to work with DTS and SSIS packages?

If those tools are derivatives of Visual Studio, if you go to Tools -> Options -> Source Control, what is the setting for the Source Control plug-in?

[dsalter]

This user is using Visual Studio 2017 (SSDT)

Plug in for Vault is:

Sourcegear Vault Standard Visual Studio Extension

Options are:

None
GIT
Sourcegear Vault Standard Visual Studio Extension
Visual Studio Team Foundation Server
Sourcegear Vault Standard Classic Client.

[jclausius]

Thanks... I'll need that to set up a test environment to match.

[jclausius]

OK. I've setup an environment with SQL Server 2017, Visual Studio 2017, and SQL Server Data Tools (15.6).

What type of project and files should I create?

[dsalter]

He selects:

business Intelligence --> Integration Services
and created a new Integration Services Project

[jclausius]

From what I can see in a sample Integration Services Project, the source control information is stored within the solution file only. The Integration Services project file stores no Vault related information in that file.

Before opening the solution, I verified my Tools -> Options -> Source Control -> "Current source control plug-in" is set to "SourceGear Vault Professional Visual Studio Extension".

Next, if you open the solution file in a text editor, and not within Visual Studio, you should see a block for Vault. In my Integration Services Project1.sln, I have the following:

Code: Select all

GlobalSection(VaultVsipSolution-v1) = preSolution
		VaultHost = http://tester1.sourcegear.com/VaultService
		VaultRepositoryID = 235
		VaultRepositoryGUID = 0C7FA119-8E29-4552-A53A-5EBAD5CE4314
		ProjectCount = 1
		ProjectRelativeDiskPath1 = Integration Services Project1\Integration Services Project1.dtproj
	EndGlobalSection

Excluding the specifics like Vault Server, Repository ID, RepositoryGUID, and project names, is that something similar to your configuration?

In my test, the solution and Integration Project were added to Vault from within Visual Studio. Afterwards, I was able to add a SSIS Packages file (Packages.dtsx), save the changes and commit them to Vault.

I next shut down Visual Studio 2017, started it back up, opened the solution, checked out the Package.dtsx file, added an 'Execute SQL Task, saved the changes, and committed the Package.dtsx changes back into Vault.

[dsalter]

Yes it is the same


GlobalSection(VaultVsipSolution-v2) = preSolution
VaultHost = http://reg2msdb0160.ad.wrha.mb.ca/VaultService
VaultRepositoryID = 2
VaultRepositoryGUID = e598fb88-feaa-4763-b7c8-c703556900a6
ProjectCount = 1
ProjectRelativeDiskPath1 = Client_Registry_DM\Client_Registry_DM.dtproj
EndGlobalSection
EndGlobal


In SSIS 2008, you could see the icon beside the package, but not in 2017.
To add a package, right click on SSIS Packages, and add a new package. Normally, in 2008 version you would see a check mark beside it to Add it to Vault.

DTS 2017 does not have any icons display beside packages.

[dsalter]

I created a MS Visual Studio 2017 project and do see the icons by the project and form.

So, this does not seem to be an issue in VS 2017, but it is in DTS 2017.\

[jclausius]

I was under the impression that only the Visual Studio family: Community, Professional, Enterprise come with the libraries and support for source control integration, and isolated shells or Visual Studio derivatives may not. For example, installing Visaul Studio 2017 Community Edition with the SSDT for VS 2017 would have what you need.

I cannot even locate "DTS 2017". Is it on the SQL Server installer? Where did you find/install DTS 2017?

[dsalter]

The install can be found here:

https://docs.microsoft.com/en-us/sql/ss ... erver-2017

I also have full Visual Studio installed, and it does not come with Data Tools.

We also use MS SQL Server Business Intelligence Studio 2008 which works fine with Vault 9 and Vault 10. We see the icons, etc. Only the 2017 has a problem.

[jclausius]

Yes. That is the page from where I downloaded and installed "SSDT for Visual Studio 2017". https://docs.microsoft.com/en-us/sql/ss ... tudio-2017

Is this the same link / tool you are using?

[dsalter]

The server we run the application on does not have internet access, so we needed to download the installation package.

When launching, it loads as VS 2017

Once installed, under HELP it says:

MS SQL Server Data Tools for Visual Studio 2017 (SSDT).
Version 15.6.4.
Using .NET framework 4.7.02558

[jclausius]

The server we run the application on does not have internet access, so we needed to download the installation package.

What link would I use to download the same installation package?

[dsalter]

I am told from here:

https://docs.microsoft.com/en-us/sql/ss ... erver-2017