Version Control - Visual Studio Team Services

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 6 years and 7 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
SDITUK
Posts: 1
Last visit: Tue Jan 30, 2024 8:19 am

Version Control - Visual Studio Team Services

Post by SDITUK »

Product, version and build: PowerShell Studio 2017 Versio 5.4.143
32 or 64 bit version of product: 64 bit
Operating system: Windows 10
32 or 64 bit OS: 64 bit

Hello,

Currently we are using TFS as our Version Control and Code Repository for PowerShell Studio 2017. As a business though we are in the process of moving towards utilising VSTS (Visual Studio Team Services) in place of TFS. Can you please confirm if VSTS is supported in the current version of PowerShell Studio or if not are there plans to add support in the near future?

It seems that PowerShell Studio currently relies on the TFS MSSCCI Provider (https://marketplace.visualstudio.com/it ... 015M-11387) but this appears to be a solution that is receiving no further development from Microsoft.

Best Regards,

Ricky
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: Version Control - Visual Studio Team Services

Post by davidc »

Yes, PowerShell Studio relies on MSSCCI providers to integrate source control at this time. Without a provider, it will not integrate directly with the IDE. We do plan on removing the reliance on the MSSCCI provider, but I'm unable to give any estimates as to when that might happen.

In the meantime, you could look at using the Custom Menu to manually submit changes to your Source Control provider.

https://www.sapien.com/blog/2015/10/01/ ... -template/
David
SAPIEN Technologies, Inc.
This topic is 6 years and 7 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.