The Seapine View

Andrew Horner, one of our Sales Engineers, was recently on-site with a customer that purchased Surround SCM, and had a large amount of source code which they wanted to import into Surround SCM from another tool. The customer had also been using a source code plug-in that allowed them to perform source code control (SCC) actions from within Visual Studio. Surround SCM has a similar plug-in that allows you to perform all of the standard SCC actions as well as other actions specific to Surround SCM, such as attaching source code changes to an item in TestTrack Pro.

In this post, Andrew explains how to bind to Surround SCM as the source code provider for an existing project. This example uses one of our sample Visual Studio solutions, Bug Reporter, that is currently bound with Visual SourceSafe, and shows you how to change the binding from Visual SourceSafe to Surround SCM Integration Provider. If you’re converting from another source code management tool, the steps will be similar.

Continue reading…

TestTrack includes Microsoft Visual Studio integration, which enables developers to work with defects, requirements, and test cases directly from the Visual Studio interface. Using one interface for your development and having the ability to also see any tasks assigned to you without needing to open another application means it takes less time to quickly address defects in code and mark the defect as fixed in TestTrack.

This video provides a quick overview of the TestTrack integration into Microsoft Visual Studio.

In a recent video I posted, I highlighted the rich feature set provided by the Surround SCM integration package with Visual Studio. In this video, I’ll show you how to easily get started using this integration.

Note that this video assumes your solution does not have any prior bindings. If yours does, you may want to review tips on how to remove source control bindings.

Download video in mp4 format

Being able to get your work done from within your IDE can greatly increase your productivity. Having a tightly integrated source code management tool with your IDE is an integral part of this. Surround SCM provides a rich feature set as part of its integration package with Visual Studio, as highlighted in this video.

Download video in mp4 format

If you are a loyal reader of this blog, chances are that you read Gerhard Kruger’s post about our Visual Studio Integration.  In this article, Gerhard talks about accessing TestTrack Pro items and Surround SCM actions from within Visual Studio. I’d like to present a different angle to this integration, specifically, the TestTrack Pro integration.
Continue reading…

This is an example of how to use the Surround SCM API to synchronize a local folder with a repository. It came as a request from one of our documentation folks, who use a tool to produce our HTML files and then need to pump the output of that tool into an existing repository.

Basically, we get a list of the files and directories and check in any existing files, add new files or repositories, and delete old files and repositories.

Continue reading…

Recently I wrote a post on the .MySCMServerInfo file, and I mentioned that one of its uses is the IDE integration. In this post, I am going to break this down a little further, and explain the Visual Studio integration with Surround SCM in more detail.  For more information, read the Surround SCM-Visual Studio integration instructions or watch a quick video of the integration in action.
Continue reading…

When companies look to invest in defect tracking and version control tools one of the first questions they frequently ask is “Do you integrate into Microsoft Visual Studio?”

This might seem like a very easy question to answer because, in short, the answer is almost always “Yes we do”.

But once people start to use the integration they normally have a ton of questions on how it works and how they would like it to work. I use Visual Studio 2008, Surround SCM, and TestTrack Pro on a daily basis so I decided to show some of the integration images with real files and bugs, as I believe that pictures speak a thousand words.
Continue reading…

A common request is to add a feature to Surround SCM that allows the user to search file contents. I have created a utility that you can use to achieve this.
Continue reading…

The following example illustrates how you can automatically generate test runs based on changed files in Surround SCM.

The program first queries Surround SCM for changes in a specified repository in a specified branch within a specified time range.

If there are files that have changed, the program then checks the TestTrack project for any test cases that have any of the files attached in the source code tab.

For any test case that has a changed source code file attached, a test run is generated for every combination of “included” test variants.
Continue reading…