Welcome to EMC Consulting Blogs

Now that Visual Studio Team System 2010 Beta 1 and Team Foundation Server 2010 Beta 1 are available on MSDN Subscriber Downloads, we’d like to announce our broad plans for Scrum for Team System. The next release of Scrum for Team System will be v3.0 and like the prior releases our aim is to ship as soon as possible after release of Team ...

As part of work recently to improve how we test the Scrum for Team System template and tools across different platforms, we have discovered there are a few additional manual steps to take when you are installing the template in a distributed environment (i.e. you are using a remote WSS 3 or MOSS 2007 server to host your Team Project Portals). ...

Update: StyleCop for ReSharper is now feature complete. While I was on holiday Microsoft released a new version of Microsoft Source Analysis for C#, in the new version - 4.3 - it has been re-branded to it's original internal Microsoft name - StyleCop. There was a bit of a backlash against the initial release of Source Analysis - a few members of ...

A colleague of mine this week showed me his code coverage as being over 94% for his production code, which impressed me so much, it spurred me on to ensure that all code paths in my code from now on go blue instead of red when testing with Team coverage, using the Test driven .NET addin for visual studio 2008. Not sure what I'm on about, then ...

It has been a busy time here at Conchango as we've been making plenty of changes to get Scrum for Team System working on Visual Studio 2008 Team Foundation Server and also incorporating changes driven by community feedback and usage of the plugin on our own development projects. We should be ready to release after we ...

There are a few things that slow down development of MSBuild-based solutions with Visual Studio.  Typically MSBuild files are named with .proj, .properties or .targets extensions - so when you drag one of these files into the Visual Studio IDE there is no Intellisense. To get around this, go to Tools > Options > Text Editor > File ...

Last week I was doing a lot of ASP.NET debugging – tracing through Microsoft AJAX web service calls and was getting a little frustrated of the time lag for starting a site in debug mode; I remembered a Visual Studio macro for attaching to the worker process and that I had rewritten in a couple of years ago to attach to multiple worker ...

The following code will get the correct database and server name for the Team Foundation Server Work Item Tracking database. Note in the call to GetRegistrationEntries you can use any one of the following ...

Looks like if you create area paths in code, then you can’t access them straight away from the item.Project.AreaRootNodes property, but have to go back up to the Store for the item, and look at its Projects collection…workItem.Project.AreaRootNodes.Count0workItem.Store.Projects[item.Project.Name].AreaRootNodes.Count2Even though these ...

EXPORT From Visual studio command prompt, issue the following command to export your work item type. C:\>witexport /f "c:\BugWIT.xml" /t myservername /p mytfsprojectname /n "Bug" /exportgloballists Work item type export complete. IMPORT - Validation First validate the xml file, using the validate switch C:\>witimport ...