As a follow on from my post yesterday about some of the intricacies of using Coded UI testing on WPF applications, I wanted to give some details about using the WpfCell class to automate validation and updates into DataGrids.
Sometimes you’ll write an WPF application that has some sort of “dynamic” way of loading portions of the UI (think: Prism). Sometimes entire frameworks are too much, so you’d prefer something a bit simpler – like, say, a TabControl with a data template. Bind the ItemsSource of your TabControl to an ObservableCollection (where T is some model) and you’ve got a “dynamic” interface.
Using the TFS API to display results of a flat query is fairly straightforward – once you have the WIQL you just execute the RunQuery() method and voila – a nice WorkItemCollection for you to enumerate over. However, if you try to execute RunQuery() on a tree or one-hop WIQL, you’ll see this error message:
This week I got an email congratulating me on becoming an MVP for Application Lifecycle Management. This is a huge honour! Thanks to all involved in this – including the community!
It’s a little over 3 weeks until Tech Ed Africa 2011 starts (it runs from 17 to 20 October). I’ll be presenting a two topics on the Development Track
Recently while working at a customer, we configured mail alerts for TFS. We checked that the SMTP server was correct and that we could send mail from the application tiers – everything looked correct, but still there were no mails.
Most posts about load balancing TFS Application Tiers using NLB use either physical servers or Hyper-V virtual servers. So you would think that you can do the same using VMWare for the Application Tiers, right?
