OK. To summarize, here are the steps I performed in the previous post:
1) I installed Visual Studio 2017 Pro from here - https://www.visualstudio.com/
(left hand side, chose Visual Studio Pro for this link - https://www.visualstudio.com/thank-you- ... nal&rel=15
) . Ran the web install.
How did you get the Visual Studio 2017 instance on the machine? Did it come from one of the Visual Studio SKUs on the links I posted above?
2) Started Visual Studio 2017, went to Tools -> "Extensions and Updates", and chose to download / Install "SourceGear Vault Standard Extension" from the "Online" section.
3) Downloaded / Installed "Download SSDT for Visual Studio 2017 (15.6.0)". During the install, for "Install tools to this Visual Studio 2017 instance:" - "Visual Studio Professional 2017" checking the boxes for "SQL Server Database", "SQL Server Analysis Services" and "SQL Server Integration Services"
4) Created a database project in this post - posting.php?mode=reply&f=5&t=23028#pr79266
If you can get to the server, you can do a "File" -> "Vault Source Control" -> "Open from Vault" from within Visual Studio 2017 to "vaultdemo.sourcegear.com" using the "guest1.. guest 9" user (note, pwd is same as login), choose the "Initial repository" and the solution found in $/VS2017/Integration_Services_Project1/. This will partially get the project on your machine.
However, since the solution has an Integration project which does not define the files it controls, you'll need to use the Vault GUI client to GET all of the rest of the files to that same working folder used by the solution/project from within Visual Studio.
Once the files were retrieved to disk by the Standard GUI client, I reloaded Visual Studio and could check out / undo check out the *.dstx files within the project.
If I were to guess, I would say the installed Visual Studio did not come from the sources I used in step 1. As mentioned in this post - posting.php?mode=reply&f=5&t=23028#pr79269
- there are certain Visual Studio SKUs from Microsoft which support integrated Source Control (or there's a bug in their other SKUs that source control does not work - depending on your point of view).
The reason I mention using the Visual Studio SKUs from the link above is that some folks are having problems when using SQL Server standalone IDEs :
https://social.msdn.microsoft.com/Forum ... forum=ssdt
https://developercommunity.visualstudio ... his-s.html
(Note, Mark Schmidt proposes a possible solution in a comment.)
Mike_F901's comment - https://docs.microsoft.com/en-us/sql/ss ... erver-2017