Come Join Polaris at CCC 2014 on April 26th

by Angela 10. March 2014 14:53

So if you haven’t been to Chicago Code Camp yet, you should! I know, I know, there are SO MANY conferences in the Chicago area, how do you choose? It’s true, there are a lot of good ones but here are some benefits to CCC:

a) Because it is community- driven, there is some amazing sessions, including a few sessions on TFS and agile. Here are the ones I am hoping to attend (to be fair I am GIVING two of those talks):


Other great sessions cover a wide variety of topics like Windows 8, TypeScript, PowerShell, Unity 3D and Azure, JavaScript and Elixir.

b) it’s FREE for a full day of techie goodness, lunch included. Yeah, you read that correctly, FREE.

c) it’s super easy to get to. It’s right off of 294 and the parking is free.

d) it’s on a Saturday so you don’t even have to miss work! OK, so maybe you don’t see this as an advantage, but I do.

e) Polaris Solutions is a Platinum sponsor and will have a booth. So stop by, say hi, and pick up one of our sweet little booklets on Agile practices.


So register now before it sells out, and check out the full list of sessions here: http://www.chicagocodecamp.com/Public/Sessions


An Upgrade is a Beautiful Thing, Especially When It’s TFS 2013 Update 2

by Angela 6. March 2014 18:09

This is one of my favorite dialogs :)


Not RTM of course, I am not THAT cool. Hopefully that is coming soon because not everyone has the freedom to install pre-release software and this one is CHOCK FULL o’ goodness. I was hoping to upgrade my company’s server last weekend, but thanks to Comcast’s unreliability I ended up barely getting it downloaded, and then upgraded my personal on-premise TFS instance. And I’m loving all the new stuff! Here are just a few of my favorite things ::cue Julie Andrews!::

1) Tags.  Tags have always been a nifty way to add useful metadata to work items so they could be easily identified, sorted, and filtered on the backlog. But everyone, EVERYONE, wanted to be able to query on tags.  Also, they wanted to work with tags outside of the WebUI.  Now you can! (requires VS 2013.w2 as well)




2) Charts. I *love* the work item charts as you may have figured out from my previous post on them.  Such a simple and easy to learn way to visually slice and dice your shared work item query results. My customers love them too! Another frequent request is “why can’t we pin these to our team dashboard?”  Well, guess what, that is an option too! So now that Team home page just got EVEN MORE useful :)  Keep in mind you can only pin charts based on the types of queries you can make a team favorite, so SHARED queries.  Also notice that now to pin something to the team homepage, you have a new option:



3) Test Plan printing. I know right?! Before your only option was Test Scribe and while it was handy, and free, it was not really customizable. Now from a quick click from the Test Hub on the web, you can request a “hard copy” of Test Plan artifacts for sharing with others via email, or as HTML. Sweet huh? And notice all the links, so an active TFS user could jump right into MTM to see or edit the items he is reading about.





There is a lot more than this, but it’s already a pretty long blog post.  So check out Brian’s blog post and the MSDN download page for the CTP to find out more about the new features available in TFS 2013 Update 2.


The Many Templates of TFS

by Angela 23. January 2014 15:41

If you are a TFS user, especially if you are a TFS administrator, then you know that with every release of Team Foundation Server that there is a rev of the process templates. And if you work on a TFS server that has gone through a number of upgrades, it is possible that your Process Template Manager dialog will start to look like this:


So many choices!! Which one to choose? Ahhhhhhhhhhhhhhhhhhh… ::cough, cough:: Back in the early days, there were only 2 out of the box templates. I know, craziness! How did people survive with only Agile and CMMI? Well, there were always the custom templates that you could get off the internet, but that is a can of worms I am not opening in this post.  For now I want to focus solely on the OOB templates.

Over the years, the templates grew up, work item types got added, fields got renamed, workflows got streamlined, and in 2010 a new template was born. But who can remember which one came out with which version of TFS? Usually it’s not a big issue until you are working on a server with lots of legacy team projects, and you need to know what the original base template was. Pro tip, the TFS Team Project Manager can really help you to answer this question AND we found a bug that they recently fixed allowing you to compare 2013 templates all the way back to 2008 templates! Well, I started keeping track, and I get asked questions about this often enough that I figured I would just share my reference.

TFS Version CMMI Agile Scrum
2005 MSF for CMMI Process Improvement 4.0 MSF For Agile Software Development 4.0 N/A -- 3rd party
2008 MSF for CMMI Process Improvement 4.2 MSF For Agile Software Development 4.2 N/A -- 3rd party
2010 MSF for CMMI Process Improvement 5.0 MSF For Agile Software Development 5.0 Visual Studio Scrum 1.0
2012 MSF for CMMI Process Improvement 6.0 MSF For Agile Software Development 6.0 Visual Studio Scrum 2.0
2012.1 MSF for CMMI Process Improvement 6.1 MSF For Agile Software Development 6.1 Visual Studio Scrum 2.2
2012.2 MSF for CMMI Process Improvement 6.2 MSF For Agile Software Development 6.2 Visual Studio Scrum 2.2
2013 RC MSF for CMMI Process Improvement 7.0 MSF For Agile Software Development 7.0 Visual Studio Scrum 3.0
2013 RTM MSF for CMMI Process Improvement 2013 MSF For Agile Software Development 2013 Visual Studio Scrum 2013
2013 Update 2 MSF for CMMI Process Improvement 2013.2 MSF For Agile Software Development 2013.2 Visual Studio Scrum 2013.2


Now, I don’t *think* I have missed any versions here.  All of the major TFS releases, and some minor releases, have been covered.  But I’d love some feedback if you notice any minor versions that I may have missed. And I’ll come back and update this when TFS inevitably gets another update, and another rev of the templates :)


Agile | Application Lifecycle Management | ALM | Scrum | Process Methodology | SDLC | Team Foundation Server | TFS | TFS 2008 | TFS 2010 | TFS 2012 | TFS 2013 | TFS Administration | TFS Power Tools | CMMI | Process Templates


Chicago ALM User Group - New years 2014 Edition

by Angela 13. January 2014 17:14

Join Us Wednesday, January 29, 2014 from 6:30 PM to 9:00 PM

In case you missed the annual Christmas Edition of the ALM user group, we are holding another special event for the New year in the Chicago location. In December, we took an Open Spaces approach to our meeting and it went very well. Open Spaces is sort of an “unconference” thing if you have not participated before, where you enter into it with no formal agenda and let the attendees decide what is important and/or interesting to talk about. So think of a topic you’d be willing to lead, or a topic you would like someone else to lead.  We will write them on a board, pick some locations for groups to gather, and then you vote with your feet, bouncing around if need be.  We had some great topics presented last month - InRelease in the real world, and automated testing tips and tricks with VS 2013 CodedUI. There was a LOT of active discussion and some great deep dives.

I’ll have lots of fun giveaways including pens, stickers, and a few more books. I’ll also have special prizes for people who lead an Open Spaces discussion during the meeting.


So I hope to see you at the Chicago meeting this month! Register soon to make sure we save you a seat: http://chicagoalmug.org/

Location:      Microsoft-Chicago 200 E Randolph, 2nd Floor, Chicago

Speaker Bio: You, me, anyone who is interested in speaking!

Agenda:       6:30pm dinner --   7:00pm Open Spaces Kickoff – 9:00pm Wrap-up


Free Training When You’re Snowed In, What’s Not To Love

by Angela 2. January 2014 12:15

So it’s been snowing in Chicago, a LOT. I am in Oak Park, specifically, and holy moly did we ever get dumped on. Here, in case you think I’m being a big baby, this was my back deck at 7am this morning and it’s STILL snowing quite hard. There’s almost 10 inches of snow on those chairs right now, and there’s a pergola over them!


Anyway, that’s not my point. My point is that I get to work from home this week, thank goodness, and ran across a great set of training classes on Microsoft Virtual Academy to fill some time. It’s free, yes FREE, and there are a LOT of technologies to choose from including ALM.  Although I’ll admit the ALM stuff is pretty light and scarce, and mostly focuses on 2012, so I’ll be nagging some folks about that soon. But there are also classes on Azure, HTML 5, even licensing!

Here is the current list of tools and technologies covered:


Clicking on Visual Studio I find a lot of great classes to get me up to speed on Windows development, HTML 5, you name it! What you see below is just the first few that came up, it’s a LONG list.


Best part is you can build up a nice little wish list since you may not have time to take everything today. So build a training plan, or several, and save the classes you like and take them at your own pace. Easy!  I already had one started from a while ago, but need to go back through and update it with some new classes, obviously :-P


So dig in by starting here. And get some of those Microsoft certifications knocked out while you’re trapped in your house by snowmageddon.


Quick Tip on Debugging TFS30139 Issues

by Angela 12. December 2013 17:27

I’ve had a few people I know run into this recently, and there does not seem to be a lot of guidance out there about process template customization, in terms of troubleshooting or tips and tricks. While running through process template updates to move clients from TFS 2005/2008/2010 to TFS 2013 I would occasionally encounter one of the annoyances of working with XML by hand:


Oh THAT is helpful.  And if you’ve ever seen the contents of a process template you know this could be one of about a million different problems in hundreds of files.

Now if you do a lot of template customizations, well just stop it, right now, please. The more you customize the more you need to maintain, the more you potentially have to upgrade by hand when you move to a new version of TFS.  There are times when heavy customization is necessary, but I often find people customize without understanding what the OOB template does in the first place. Unless you are checking your templates into source control, being very methodical about isolating changes and testing, and commenting your changes just like you do with your application code, you’re going to run into problems during upgrading. But chances are you’ve already gone down the path and here you are…

Enter TFS consultants. I prefer to do most of my process template editing directly against the XML using Notepad when I can. I know, it’s a bit old school, but there are a lot of us out there so I figured why not share? Inevitably, you misspell something, miss a closing bracket, enter an errant blank space where it does not belong, the common XML “bugs” that can be really difficult to track down.  And as you know, Notepad does not have a debugger.  So like me, I’m sure at some point you’ve tried to upload an updated process template using the TFS Process Template manager and seen the dreaded “TFS30139: The process template is not configured properly.” ::SIGH:: Now what? Well, if you followed my previous advice and were methodically checking in distinct changes, you know what you last changed. Kind of like CI for process templates :)

Enter the power tools. The TFS Power Tools contains a great process template editor that you can use in place of a lot of the command line tools for importing and exporting work item type definitions. You’ll need to install it on a machine running Visual Studio Professional or better, FYI.


It gives you some great visualization tools, allowing you to edit fields, configure the forms, visualize and edit workflows, states, and transitions, and an easy way to open and dig through all the nitty gritty details of everything else that a process template entails too.  As an added bonus, it will give you MUCH better error diagnosis information if something is wrong. So for the previous error, I attempted to open the process template. But this time I got a much more friendly message, pointing me at the issue:


Because I knew that the last thing I changed before my last successful upload of the template was the ProcessTemplate.xml file. I knew exactly where to look and lo and behold, I’d left off a closing bracket at the exact location specified by Visual Studio. So I made the quick fix, successfully imported the updated template to the collection, and checked in the updated template file to SCM. Much better!


There are lots of potential tools and editors out there for process template editing, and everyone develops their own style. I often find myself leveraging several different tools in conjunction during a process template upgrade, it can be a lot of trial and error.  They all have advantages and disadvantages, I’ve tripped over a few myself (like this little quirk with the Team project Manager extension if you’re trying to compare 2008 and 2013 templates). I should blog about some of those adventures too :)

Hopefully this gave you some new options you may not have been aware of before.


Trying Something new with the ALM User Group in December

by Angela 3. December 2013 13:50

So it’s time again for the annual Christmas Edition of the ALM user group. Normally we do the normal “dinner and a movie” approach, maybe having a special guest speaker or some kind of presentation contest. This month I wanted to do something different.  In December, we’ll be doing an Open Spaces concept. So Open Spaces is sort of an “unconference” thing, where you enter into it with no formal agenda and let the attendees decide what is important and/or interesting to talk about. So think of a topic you’d be willing to lead, or a topic you would like someone else to lead. A few I’d be interested in talking about are transforming organizations to Agile, upgrading legacy systems to TFS 2013, and agile testing.  We will write them on a board, pick some locations for people to gather, and then you vote with your feet, bouncing around if need be.

As an added bonus, if you’ve been attending the ALM user group for a while, you know that December is “Angela cleans out her SWAG closet” month.  So I’ll have lots of fun giveaways including pens, stickers, mouse pads and LOTS of books. I’ll even have special prizes for people who lead an Open Spaces discussion during the meeting (think XBox/Kinect games, Arc mouse, T-Shirts).

So I hope to see you in Downers Grove next week.  I always enjoy our December meetings, and not just because of the cookies :)

Be sure to register soon so I can order the right amount of food!



Join Us Wednesday, December 11, 2013 from 6:30 PM to 9:00 PM
Location:  Microsoft-Downers Grove 3025 Highland Pkwy, Ste 300, Downers Grove

Speaker Bio: You, me, anyone who is interested in speaking!

Agenda:6:30pm dinner 7:00pm Open Spaces Kickoff

RSVP Now to Attend


Building Software, One Room at a Time

by Angela 30. November 2013 21:33

Comparing software development to “building a house” is one of those analogies that sets my teeth on edge. It oversimplifies everything that goes into designing and building a good product, and it also creates some unrealistic expectations in terms of estimation and effort, both for development and testing. I heard it yet again recently, and it just shocked me that it’s still being bandied about these days. C'mon, don’t act so shocked, you probably have said it yourself or heard it said at some point. I know I have, on both accounts. And you know what, it's OK, I’m not here to judge you. Unless you are still saying it, then I will judge you quite harshly :)

There was a time when this was far more true of an analogy than it is today. As someone whose original passion was "architecture", as in, creating blueprints for houses, it made a lot of sense.  Plans are good, and who doesn't like structure and rules? You see, there was a time when software was created by pouring over designs for the right "feel", sometimes for days or weeks to establish a solid foundation. Remember when SOA and OOP were the hot new things?  Before a single line of code was written we had UML diagrams and if we were really fancy stubbed out methods for the developers. And sure, when building a house every angle is inspected, measured and re-measured, the location and size of every supporting wall is verified, every window placement is compared to housing codes, all before a single piece of wood was sawn or hammer was swung. Then contractors are set loose with the specs to build the house according to a well laid out plans. Except what if by the time it was delivered, the homeowners didn’t want to actually live in the house they asked for in painful detail without some major rehab? The colors are all wrong, the yard is too small, the garage is too narrow, there aren’t enough bedrooms. Could you imagine?! In home construction, nobody sane would do that, and yet it happens all the time with software. Well, there you have it, the analogy is already somewhat blown. But there's more.

You know you've been on THAT project. You know the one - late, way over budget, customers are screaming that it isn't what they asked for even though you have signed requirements specs that say it is. Heck, even if you are just NOW getting into software development you're probably going to experience this still at some point. Particularly if you work someplace that is still stuck in a Project Plan driven mentality, a.k.a. "Waterfall" ::cue dramatic music::  Who just let out a little shudder? Now don't misunderstand, I'm not a hater, waterfall-based methodologies can work well in some scenarios, but generally even waterfall enthusiasts are not following a strictly traditional waterfall approach. And to be fair, even "real" waterfall, as I learned it back in college in the late 90's, dictated iterative practices. But often that little nugget gets lost in translation in favor of forever marching forward through a seemingly unending tunnel of quality gates, attempting to hit arbitrarily established milestones. So back to my original point. Building software is not just like building a house, or maybe the more correct way of conveying my thoughts is that building software SHOULD not be like building a house. And if it is at your company, I do not want to work there. Unless you're looking for me to facilitate an intervention of sorts. Let me explain...

Imagine you want to have a custom house built. And let's say you already know more or less what you want. Tudor style, 3 bedrooms, 2.5 bathrooms, eat-in kitchen, with a detached 2 car garage. Maybe you even have an existing blueprint because plenty of houses like that already exist, so why re-invent the wheel right? Work begins, and the house starts becoming real. But even after several weeks of work, while things may start to look like a solid shell of a structure, you cannot live in it.  Well, not legally anyway. There is probably no plumbing yet, certainly no electricity, perhaps the roof is not even yet in place. You also cannot decide you now want something more Spanish style, single storied and sprawling, with an attached garage and a courtyard garden in the center. Well, technically you COULD decide to do that but it would require MASSIVE structural rework, new permits, perhaps a different construction crew, and of course SIGNIFICANTLY more time and funding to complete. OK, so I suppose this is one parallel you can draw to software development, but again this is more of an issue in waterfall shops, particularly if you are already deep into development before someone realizes a much earlier decision was a poor one. Many thousands of man-hours will get wasted, people may lose their jobs, customers will be unhappy, and you likely will end up with a Spanish tiled, Tudor style home with a semi-attached 2 car garage that has a courtyard in the center of it. So with building a house, you will not realize the value of the product and be able to use it until the last finishing nails are hammered into the last room, and major feature change requests will almost always be unfeasible to honor even early on in the construction process without MASSIVE negative consequences. Do you want to build or pay for software that is built that way? I certainly don't. 

I don't see housing contractors ever building homes one fully functional room at a time, allowing the home owners to live in it long before it is finished. I do not see them redesigning the blue prints and only ordering enough supplies for each room about to be built to incorporate changing design trends, evolving safety codes, nor do I see them accommodating the ever-changing whims of the owners.  "Oh. You've decided you want an open floor plan instead of separate kitchen and dining rooms? No problem, we're just finishing the main bathroom and haven't even framed the rest of the first floor yet..." Yeah, no. I also do not see those contractors getting the homeowner's signoff on each finished component before moving on to the next one, incorporating feedback and change requests, continuing this iterative process until the house is complete. Maybe you're thinking, "well, we don't have the ability to do any of those things today when we design, code, test, and deliver software either". I'm sorry to hear that. We should talk, there's a 12 step program to help you, and you've already admitted you have a problem which is the first step to recovery. Well, there ISN'T a program, sadly, but I often joke that there *should* be.

Now this is an easier problem to solve in software. Software teams CAN be flexible, adapting to changing needs of end users. Software can be delivered in small, working, usable pieces to deliver value as soon as a few weeks after the project begins. And it doesn't have to cost more. It can actually cost FAR less if you do it right. This is part of the reason I am such a proponent of Agile and Scrum. But honestly that is another topic and this post is already long enough so we'll defer that conversation for now.

So here is one place where building a house and building software ARE remarkably similar.  Estimates. Regardless of what a contractor tells you, no one knows for sure exactly how long building a house (or software) will take. Sure we can ballpark it, but every job is different. People will sometimes push back and call that a copout consulting answer, but it's the truth, and I try not to make a habit of lying to the people paying me to work for them. And if you demand exact delivery dates, are unwilling to compromise on features (maybe the rotating shoe rack in the closet really isn't NECESSARY), and have immovable end dates, well, you may want to refer back to the 12-step program that I mentioned earlier. No one can account for bad weather, people getting sick, catastrophic hardware failures, or that the latest version of the .NET framework that was just released has added complexities that cause even the most experienced programmers to take 50% longer to get things done for a few weeks. Should you go so far as to expect the team to commit to dates, deliverables, AND cost - to the point they take a hit if any of those things slip - well, prepare yourself for a sandbag big enough to hold back a hurricane, or to have people eventually seek alternate employment. NO ONE wins. And yet these kinds of unrealistic expectations reoccur everywhere I turn in the tech world. Maybe someday more software teams will be able to hold stakeholders and end users accountable for the quality of requirements, and refuse to take on change requests after work has begun without serious concessions, seems logical and fair. Ahhh, dare to dream :)

So now can we stop comparing software to building houses? Please and thank you.


Application Lifecycle Management | ALM | Agile | development | Process Methodology | Scrum | SDLC


These are a few of my favorite things about TFs 2013: Part 2

by Angela 12. November 2013 07:53

So hopefully you already caught part 1 where I extolled the virtues of Work Item Reporting. This time, I have moved into new territory!  I am in the middle of a big, slightly nasty, TFS upgrade and TPC consolidation project.  First thing is first. Attaching a legacy Team Project (TP) to TFS 2013 “upgrades it” but only in the sense that it works on TFS 2013. So you get everything you had before, but not necessarily ALL of the new stuff in 2013.  You probably have very little of the new features in terms of the “agile planning tools”. There were changes made to the underlying TP Process Templates to support new features like, the “Feature” feature :)

I apparently had been taking the TFS Configure Features Wizard (CFW) for granted. “The what?” you say…  Yeah, the thing that gets launched when you upgrade to TFS 2013 and you try to open something like the Product Backlog while connected to a legacy (pre-2012) TP. So if you’ve seen this message, the link at the bottom launches the CFW:


Often if you have an older, customized template (like modified CMMI 4.2), you can run into issues with the wizard.  You may be familiar with errors like this “[Error] TF400654: Unable to configure Planning Tools. The following element contains an error: RequirementBacklog” or “[Error] TF400654: Unable to configure Planning Tools. The following element contains an error: TypeFields/TypeField[type='Order']“. Makes sense, there are some HUGE deltas between older templates and those in 2013.


So the CFW is super easy to use if you can upgrade with the OOB templates, especially if you’re just upgrading one version behind. And how often does THAT happen in the real world? Right. In our case we have TPs coming from TFS 2005, TFS 2008, AND TFS 2010 and all the templates are customized versions of CMMI. Oy. I decided to begin by upgrading the 2010 TPs since they were the most straight-forward and had the least amount of differences as compared to CMMI 2013. So, that is the main focus of THIS post.  I will share experiences IRT other template versions later.  So if you start with MSDN you’ll see a tangle of different articles when it comes to upgrading to new templates. A few important points about process templates:

  1. A) In case you did not know, you can’t just swap templates out once you have created a Team Project and started using it, you HAVE to upgrade the underlying template of a team project itself to make changes ::opens giant can of worms:: OR if it’s a major change, like going from CMMI to Agile, just trust me on this -- migrate to a new Team Project.
  2. B) Template upgrades can be scripted but at the end of the day it is very manual, and fairly time consuming because of all of the testing required.  XML can be tricky for even the saltiest of us developers.  In the old days it was ALL manual all the time and all command line, but over the years a host of helpful add-ons have become available like the process template editor in the TFS Power Tools, and the TFS Team Project manager tool.
  3. C) Changes to a base process template (so at the TFS Collection level) do not automatically filter down to TPs created with that template, wouldn’t that be awesome and terrible at the same time?!  You must manually apply any template changes to all TPs that used that template, if you want them to remain consistent.  I bet now you really regret spinning up new TPs for every single one-off project your IT group dreamed up huh?


But now there is another way, the Configure Features Wizard ::duh duh DUUHHHH:: I will admit, I did not thoroughly RTFM the first time through and missed out on the full power of this little tool myself. To be fair, the last time I had a massive mutli-version TFS consolidation this tool didn’t even exist.  Of course now that I know what to search for, I turned up this AMAZING post of Edwald’s on how the wizard works, as well as this MSDN article that details how it is working its beautiful magic under the covers.  To sum up why it is so awesome, it allows you to specify your template changes once, and then easily rinse and repeat with a click of a button. No scripting or command line necessary. Unless you like that sort of thing, or have a bajillion TPs, then have at it, but use this handy script to iterate through all of your projects.

So how does it work? I still contend there is some black magic involved, but more likely it was a lot of late nights by some wicked smart TFS dudes. Essentially, you need to create a new copy of the legacy template that was used to create the team projects that you wish to upgrade to 2013, and then retrofit some new shinies from both 2012 and 2013 into it. I first downloaded CMMI v5.0 (which they had customized and re-uploaded without renaming – ACK!). Next I had to do things like add in a handful of work item types (Code Review and Feedback for 2012, Features for 2013), update my WIT categories, as well as add the Process Configuration file specific to 2013.  For all other work items I was able to simply replace the 5.0 WIT definitions with the 2013 versions, and then retrofit the client’s customizations back in. I used the heck out of the Team Project Manager Tool to compare them and see exactly what was customized.  Be careful here and read both the 2012 changes AND the 2013 changes that need to be incorporated, so you don’t duplicate effort.  For instance, the 2012 changes have you add 2 configuration files, but then both of those files are replaced by the single Process Configuration file for 2013. When I was done, I had a new version of the process template (with a new name!) that I could use with the wizard to convert the old TFS 2010/CMMI 5.0 TPs to 2013. It also contained all of the customizations that were done on the template before the TPs were created.  Last, I uploaded that bad boy to the TFS Server, navigated to my legacy TPs one-by-one, and launched the Configure Features Wizard. I ignored the recommendation of CMMI 2013, and picked my updated CMMI 5.0 template:


When the wizard runs, the super-simplified explanation is that it performs a DIFF on the team project and the modified process template, and applies the changes to the TP so it now matches the template. I KNOW!! So update the template once, run as many times as you need.


Now, if after the team projects were created off of that old template, you had some template cowboys who went in customized the crap out of team projects in an inconsistent manner, or did not also make that change to the underlying base template as well, you may end up needing to upgrade those team projects by hand and/or resolve any issues encountered during the wizard to upgrade them to 2013 completely. No easy button there. And maybe start being more careful about who you let customize process templates and team projects going forward! ;)

Now you have a simple way to upgrade all of the team projects created off of that old, custom template up to 2013.  At least for 2010.  Next we tackle all of the 2008 TPs.  And my understanding is that if you have 2005 TPs, just play some Taps and migrate what you need to a fresh, new 2013 TP.


Application Lifecycle Management | ALM | Power Tools | SDLC | Team Foundation Server | TFS | TFS 2013 | TFS 2012 | TFS Administration | TFS Power Tools | TFS Upgrade | Visual Studio 2013 | Work Item Tracking


St. Louis Day of .NET is Next Week - Sign Up Before It Sells Out

by Angela 5. November 2013 23:32

I’ve been hearing about St. Louis Day of .NET for some time now but up until recently I just hadn’t thought to attend.  I mean, we have TONS of events in Chicago, so I always made excuses.  This year, Polaris Solutions has stepped up to support STLDODN as a Platinum sponsor.  We're planning on not only participating, but we have a few folks speaking, and we are even hosting a booth so be sure to stop by and say hello! I’ll be the redhead, also, the only woman in the booth so I’m easy to spot :)  If you wanted to catch one of our talks, here is the run-down:

Chris Kadel will be participating in the TFS pre-compiler on Thursday Nov 14th from 8:30am to 5pm: http://www.stldodn.com/2013/pre-compilers.  It is a FULL-DAY hands-on workshop and it’s only $75 to attend, so sign yup fast. You can’t get training like this for such an amazing price anywhere else that I know of.

A Pragmatic Intro to Unit Testing by our very own Josh Gillespie

Advanced OOP by our newest team member and former Softie Clint Edmonson

Agile Testing in a Waterfall World by your truly!

Application Architecture Jumpstart also from Clint

Dude I Just Stepped into Your Code from Josh


If you haven't registered yet, click on "Register Now!" at the top of the website and find out why people love this event so much.  http://www.stldodn.com/2013/what-is-the-day-of-.net.

Powered by BlogEngine.NET
Original Design by Laptop Geek, Adapted by onesoft