On the seventh day of Christmas, my true blog gave to me… seven Team Services features!
…six GIFS a-dancing, five Golden Rules!
Four Community Sites, three Maturity Models, two Sitecore PaaS features, and Sitecore in a NuGet feed.
If you have been using Visual Studio Team Services, you know that Microsoft regularly releases new functionality to the application throughout the year. Today we’ll recap seven new features released in 2016! These may not be the biggest changes, but they are the ones I like to see in the evolution of a product.
Continue reading “Seventh day of Christmas… VSTS features in 2016”
SPECIAL NOTE: This article is a lead up for my November 30th #SCUniversity session on Continuous Integration and Deployment. Register for the webinar now!
When you are setting up your Continuous Integration build definition in Visual Studio Team Services (VSTS, formerly Visual Studio Online) you will get a NuGet Restore step that by default will work with any standard NuGet feeds. However, if you try to build your solution with Sitecore NuGet references it can’t download the packages. Time for your NuGet.config!
Continue reading “VSTS and Sitecore NuGet feeds”
Recently I needed to get builds running in Visual Studio Online (VSO) that contained Team Development for Sitecore (TDS) projects. Since I cannot install the TDS software on the VSO build server, I needed another way to get these projects to compile with a VSO build definition.
The following blog post has very detailed instructions on how to change your TDS project to use Hedgehog DLLs and a license file within your source control and helped immensely:
The referenced post indicates that you should update a file named TDSLicence.config in order to provide your TDS licence key. This file does not exist by default, so you will need to create it. The file name is important! I accidentally created the file with the American spelling ‘TDSLicense.config’ and the build server was unable to validate the file. Hedgehog support helped me out by pointing out my typo, but also explained that version 5.1 and up will support both spelling variations.
Recently, Aaron Bjork wrote about some of the goodies coming down the pipe for Visual Studio Online (VSO) agile project management options. I still remember my first forays into TFS 2010, trying desperately to use it to manage my agile projects.
Needless to say, I was frustrated at the time, but today is a new day!
There are a lot of things coming like Kanban board improvements, hierarchical backlog management, and task customizations. Fun goodies to play with for all 🙂
Continue reading “Visual Studio Online agile options are opening up”
This past Tuesday I attended a Webinar led by ALM Ranger and Microsoft MVP Esteban Garcia (@EstebanFGarcia). The topic? Azure and Visual Studio Online (VSO), specifically around deployments (or so I thought). There was more content in this session than I expected to get, that’s for sure!
My primary goal in attending the session was to get a better picture of how deployments worked from VSO code repositories into the Azure cloud, but as a bonus there was also coverage of VSO load testing functionality, as well as Application Insights. Continue reading “Visual Studio Online and Azure deployment”
About a month ago, I mentioned that Visual Studio Online was making some licensing changes to better integrate the greater project team into the tool. The Stakeholder licensing changes were announced as live this past week. Of course this happened while I was away on vacation!
I have a theory: the best way to make something happen is to go do something else. So I spent the last couple of weeks road-tripping, hence the lack of new content the last few weekends. Lo and behold, the Stakeholder licenses arrive! Continue reading “Visual Studio Online Stakeholder licensing is live”
Last week, Brian Harry announced on his blog some upcoming changes to the Visual Studio Online licensing. Word is that the changes should be coming in the next few months (an August-like timeframe is mentioned). The announced changes are going to be a great help in positioning Microsoft against some of their competition in the Application Lifecycle Management (ALM) sphere. How they went about deciding what change to make is just as interesting.
Continue reading “Upcoming VS Online licensing changes greatly helping Microsoft’s position”
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”