Microsoft has created some guidance on how to do Sharepoint development when using TFS. Sounds great if you’re into Sharepoint! (as I am these days)
This is one major version of the TFS Power Tools! I’ll need to read the blog post again to take it all in, but at first glance it looks like a great update! Powershell support is nice, Shell integration is OK and the Team node looks incredibly useful! Looking forward to the first CTP!
This is good collection of tasks for MSBuild, nice to know about.
# The Suite provides over 170 tasks covering the .Net Framework, BizTalk, FxCop, IIS7, SourceSafe, StyleCop, Team Foundation Server, WMI and more. # Every task is provided with clear documentation and a working sample. Where applicable, tasks also provide remote support, e.g. IIS7, GAC etc. # The Suite can be installed via an MSI for easy and consistent deployment.
Perhaps the biggest call we made for Rosario was to drop support for SQLServer 2005. Rosario will only support SQLServer 2008 and later. That was a controversial decision but it is a final decision. The primary driving force behind it is that the Report Server feature in SQLServer 2008 is sooooo much improved over that in previous versions that we simply could not pass up taking advantage of it for Rosario.
Huge change in the next version of TFS! No support for Sql Server 2005 is huge! Hope everybody is getting the message!
If I were to deploy TFS now and be prepared for the future I’d order two boxes; one with Hyper-V installed and running a VM with Windows Server 2008 and the application layer installed. The other box would be a W2K8 with Sql Server 2008 on. On box number 1 I’d also add at least one more VM to use as a build server. depending on what kind of software you’re producing you might want a third VM for test installs of your software (ISV). Hyper-V is cheap, fast and simple. It lacks a bit compared to VMWare ESX, but that’ll come in v.Next. I believe the 80/20 rule is in effect here.
This is the start of a mini series during which I will review the Rosario CTP Mini-Stories, viewing it from our production perspective and highlighting exciting, missing and/or troubling features. So let’s rock and roll with the latest and greatest of Team Foundation Server
Ahh, the next version of TFS! Cool! Have a look at part 5; no more Xml for you! 😉
This solution was developed to address the need to automatically propagate specific files in the Team Foundation Server version control to a predefined path.
Could be useful, in my old job we could have made use of this to make sure our shared binaries/task/etc. was always up to date. Instead we chose to use xcopy…
Pretty cool! I like the fact that they (Microsoft) are actually showing us their specs! That’s just awesome! Charles asked for feedback on whether we wanted to see more spec like this or not; my answer is a simple yes. It’s awesome to see how Microsoft does this and to see what you guys are thinking. How will VSTS/TFS look/feel/act in the near future? All good stuff!
As for the features; The bug submission feature doesn’t really attract me all that much, but it looks like a nice feature though. The linking spec was just too much for me, I lost track after like 3 minutes of reading. Looking forward to a new drop of Rosario CTPs to test though. The e-mail feature looks nice, especially when paired with TSWA. Not sure how I feel about the requirement to use Outlook though… Could this be done in a more open fashion?
Something just dawned on me; why aren’t WI queries available as RSS feeds? That would be an awesome feature!
I’ve always wanted to use Scrum and TFS/VSTS together, I wonder how good this template this is?
We should probably add “Testers” and “Devs” to our list. That way we don’t have to know/care about where to send items, just that some dev/test person will pick it up. Add some notification magic and you can make sure that the correct people are notified when they should. Easy does it!