Recently, while trying to synchronize with my Visual Studio Online git repository, the Visual Studio Git plugin started displaying the error “URI formats are not supported” while attempting to execute a pull operation. This appears to be an issue introduced with Update 2, and at least from my own experience only appears to be affecting Pull operations.
This issue appears to be manifesting in my case due to either a web application or WCF service application that I added to my solution and synchronized to the repository. If you’ve done something similar, you’ll probably start seeing this error as well. After this error occurs, push synchronizations will continue to work, but attempting to pull changes or use the ‘Sync’ operation on the remote repository will fail with the error message.
The issue has been reported to Microsoft back in May and a few workarounds have been posted, including a suggestion to use another tool like SourceTree to execute your repository synchronizations.
UPDATE: Microsoft has stated that this issue will be resolved in Visual Studio Update 3.
For the last year or so, I’ve been living in a mostly Atlassian world: JIRA OnDemand, BitBucket, SourceTree… likely more before the year is done. Sure, I still use our on-premise TFS 2010 at work along with Visual Studio of various editions, but my ALM world has really been rocked by those gorgeous tools from Atlassian. This past Friday I should have been doing something productive (like writing a blog post) but suddenly I was captivated by the world of Visual Studio Online. Continue reading “How Visual Studio Online won me over in under 90 minutes”
While I was at the ALM Summit in January, Claude from InCycle (now with Microsoft) was doing demos of their InRelease software. The deployment software allowed for a massive amount of deployment configuration, moving a build between labs and retaining environment-specific configurations using a tokenized language. The workflow definition for how the build should flow from environment to environment also allowed for accepting or rejecting the build.
I was impressed at the time, and obviously Microsoft was as well, since they started the process for acquiring the product a few months ago. As of July 10th, the acquisition is official.
This means InRelease will soon become a full part of Visual Studio and Team Foundation Server 2013. The preview download is available from the InCycle website.
There was no way that I could resist downloading the D&D process template posted by the TFS product team on their blog. I absolutely NEEDED to see what had been done inside here. The blog post was very bare on the details, but it seems that with a few configuration changes this process template can help to make your daily work a little more fun.
Here’s what I was able to find by digging through the files in the ZIP that you can download:
Continue reading “Dungeons and Dragons TFS Process Template”
During development, your team makes a lot of changes to fields, templates, presentation details, and various other elements that need to be tracked, verified, and deployed. You need a way to source control those database changes, and then make them available to your team to test. Here’s how to accomplish that using Team Foundation Server (TFS) and Team Development for Sitecore (TDS)!
Sitecore content items in source control
Our teams use Team Development for Sitecore from Hedgehog Development to create .NET TDS projects to source control the changes we make in the Sitecore database. There’s a great guide from Hedgehog to start with, and I’ve previously written a post on some project configuration basics.
Automating deployments of Sitecore content items
With your content items now in Source Control, you can start getting your database changes deployed along with your build.
Note: This assumes you are automating your file deployments to push code changes out to your environments. If you aren’t yet, you should be! Look for my upcoming posts on setting up deployment build configurations.
In order to get TFS to be able to deploy, there are a few things you need:
Continue reading “Automating Sitecore Deployments with TFS and TDS”