Today we launched the new Microsoft Developer Network site. As I’ve mentioned before, my team is responsible for much of the infrastructure and experience for MSDN. I’m very proud of what we have and at the same time see opportunities for improvement.
Sometime this spring, though for the life of me I can’t find it, I wrote a blog post where I said I thought Update 3 (VS/TFS 2012.3) would be the last update in the VS/TFS 2012 update line. I often say that nothing that is said about the future is more than a guess with varying levels of confidence.
It wasn’t until after I posted my “news” post this morning and I was perusing our news site that I realized that the first news post was almost exactly 1 year ago on August 6th 2012. These are precisely the kinds of things that sneak up on you unawares.
Today we released an update to our Visual Studio 2012 tools for Git. We’ve been iterating on these since the first release in February and each release gets more complete, easier to use and better performance. Of course that same tooling (though it’s a bit older release than 0.9.5.0) is included in the VS 2013 preview and more recent version will be included in the VS 2013 RTM.
Today we are deploying our sprint 51 build. You will soon be able to read the release notes here. Today’s deployment is what I’d like a lot of deployments to be like – nothing particularly big but a bunch of nice improvements.
We are gradually working our way into goats. Last year we bought a dairy goat and she had 2 kids. This year we bought 2 meat goats (Kiko breed) and one of them, “Pretty Girl” just had 3 kids. I thought I’d share some pictures.
Visual Studio has always been a great tool for developers. In 2010, as we continued to expand the breadth of our Application Lifecycle Management suite, we made our first foray into tooling specifically for testers with Visual Studio Test Professional. Thus started a journey to really incorporate testers into the application lifecycle,
I had someone ask about this so I decided to go ahead and post something. Below is the contents of a Word doc that describes our REST API for working with Team Rooms. It should work both on Team Foundation Service and on a public preview of TFS 2013.
Last week we completed sprint 50 and, today, the changes went live on the service. You can read more of the details of what’s new on the service news feed.
One of the things I’ve had to get used to with a service is the notion of publishing features that aren’t nearly finished.
At TechEd, in early June, I announced our agreement to acquire InRelease – a release management product built specifically for Team Foundation Server by InCycle Software. Since then, we’ve received tons of requests for more information, demos, etc. Unfortunately, we’ve only been able to point people at InCycle because the acquisition was not final.