Archives / 2005 / November
  • Team System Code Coverage and Manual Tests?

    No problem...

    1.  Turn on Code Coverage in your app
    2.  Launch the Manual Test from the Test Manager
    3   Use the Windows Explorer to find the target app and run it manually
           eg.  If you build to Math\bin\debug\math.exe - launch manually from this location
    4.  Follow the instructions in the manual test - pass or fail it
    5.  Shut down the app
    6.  View code coverage results


  • November 29 Release of the PTE

    November release of the Process Template Editor - bottom line, lots of changes and bug fixes.


    Icons for All Windows
    "for" and "not" should be renamed
    Areas and Iterations Map to Definitions
    Duplicate Names
    Bottom half of Groups and Permissions doesn't seem to be working
    KABOOM: Creating New Item in a Document Library
    Change the Infragistics Controls
    Drop Down for Title field
    Areas and Iterations to display hierarchy
    Work Item Rendeing seems off
    States and Transitions Fix
    Editing Layout
    Reportable Fields Fix
    Permissions KABOOM
    Clicked on New button
    New Document Library doesn't work
    Right Click on existing library
    Able to change extension...
    Adding new report should allow me to select a existing report file
    No minimum size on the work item type window
    Sizing Work Item Dialog does not size controls
    Adding New Transition does not allow for a reason
    Able to Add a State that Transitions to itself
    Work Item Type validation rules should not only be a function of the GUI
    No minimum size for main MDI window
    Online Global List saving should have a timer mouse icon
    Tree Navigation for entire application


  • Automating Web Site Builds with Team Build

    Using Team Build to Build an ASP.NET Web Site

    So – you’re a web guy – good for you! – no – really – I mean it.  You like ASP.NET – Excellent.  You heard about this Team System hubbub and think to yourself “nice…” and dive into the automated build world that is provided with Team Foundation Server.  You follow the rules by creating a Solution Structure that contains a web site – you add it to Team System’s rocking new source code repository and jump into the Team Build Wizard to go and create a new automated build (after you install Team Build on a separate computer of course).  You run through the create build definition wizard – and you can literally hear the villagers dancing in the streets!  You go and kick off the build through the Visual Studio Team Explorer – and… it doesn’t work.


    Very common problem apparently.  First of all, check out the properties of your solution file…specifically Configuration Properties->Configuration.  Here you will see a list of your projects, their configurations and platform.  Notice how your web app’s platform is .NET.  Hmm… did you even see that option when setting up the automated build?  Nope – ya didn’t.  You only had the ability to select Debug and Release and to select from a platform list that included the Itanium, but not .NET.

    So, is there a solution?  Sure… I guess.  What I’ve done to fix the problem is to remove the following section(s) from the TFSBuild.proj file that essentially helps to define the Build definition (this is stored in source control under “Team Build Types\><NAMEOFYOURBUILD>” in case you were wondering).

        <ConfigurationToBuild Include="Debug|Any CPU">


          <PlatformToBuild>Any CPU</PlatformToBuild>


    This will force the Mr. Big Build to use the configuration defined in the solution file.  You can alternatively change that section to the following:

        <ConfigurationToBuild Include="Debug|Any CPU">




    So, this get’s better – suppose you have a solution that has a web site as well as a bunch of libraries.  Well, in this case you have a mixed set of configurations and platform targets don’t ya…

    Try this:

        <ConfigurationToBuild Include="Debug|Mixed Platforms">


          <PlatformToBuild>Mixed Platforms</PlatformToBuild>


    In truth, these options should appear in the Team Build creation wizard.. but for some reason that’s not always the case.  Also, don’t discount the importance of the solution structure and your web site – you need to ensure your website is contained within the solution structure.


  • November 21 Release of the Team System Process Editor

    Here is the latest release. What's changed? Well, we ripped out all of the Infragistics controls for one. We've also added lots more validation (when online) as well as user interface enhancements to help prevent you doing crazy things that is allowed in the resulting XML but you would never want to do in real life. We've also added Global List support. Our next release is next week where we will be rounding out more corners specifically around Global List support as well as Work Item Type field level support (not to mention making it look nicer - adding the missing Menu features, etc). You can get it from the GDN Workspace or from our web site... Note, I have completely opened up membership to the GDN Workspace... I kept running out of memberships to give out...


  • Get Ready Edmonton and Victoria...

    .. because you are about to get rocked!!!  The Visual Studio launch is hitting those cities on November 15th (Edmonton) and 17th (Victoria).  I've been zip zagging across this tiny planet (literally) for the past year and haven't spend much time in Canada.  Because of this I'm really stoked to say that I'm co-presenting along with the LEGENDARY John Bristowe who decided to take a ride on the wild side and go work for Microsoft Canada.   John has recently delivered the launch event in Toronto and Ottawa - and let me tell ya - the man is on fire!!!  I only guarantee two things.   You will learn - and you will be entertained!!!


  • Visual Studio Launch and What it Means to Me

    I’ve been playing this Software Development game for almost 15 years now yet I can’t deny that I still get excited about new technology.  This is the week of the Visual Studio 2005 Launch (along with its close cousins SQL Server and BizTalk 2006).  I’ve been working with these products for more than a year now – traveling all over the world educating customers and helping them understand how these products can be adopted and leveraged in their world.  Some customers simply can’t wait for the next version of SQL Server; others believe Team System will be extremely valuable to their organization.  If there is one thing I’ve found over the last year+ is that every customer truly has distinct and specific needs.


    What do all of these new products mean to me?  Well, for me these new products signify a new opportunity to innovate and grow.  They symbolize another jump start on the global economy of software engineering and that excites me.  On that note, I thought I would take this time to highlight some of the product features that I’m really pumped about.  If you are attending any launch activities around the world you will undoubtedly see most of these:


    NOTE:  the following aren’t all the new features of the products, simply the features that stand out in my mind.


    1. Team System:  A new collaborative platform that provides us with the opportunity of truly focusing on the quality of our software and the processes we use to construct it.  Specifically my favorite parts of Team System are:
      1. Team Foundation Work Items
      2. Team Foundation Team Build
      3. Team Foundation The Team System Data Warehouse and Reporting Services
      4. Team Foundation Process Templates (powered by my Process Template Editing software of course)
      5. Team Foundation Source Control (a must have in my opinion)
      6. VSTS for Software Testers: Load Testing
      7. VSTS for Software Testers:  Web Testing
      8. VSTS for Software Developers:  Unit Test and Code Coverage
    2. SQL 2005
      1. XML Data Types
      2. Try Catch Error Handling
      3. Common Table Expressions
      4. Native Support for Web Services
      5. Stored Procs as Managed Code (even though I think this can be dangerous)
    3. BizTalk
      1. WAY easier installation and initial configuration
      2. Much better Orchestration experience
      3. Better MOM Support
      4. HUGE Business Activity Monitoring Improvements (this stuff makes me warm and crazy inside)
      5. “WOW” style performance and scalability improvements
      6. Lots more operational and management features
    4. ASP.NET (I’m not a web developer, but using ASP.NET 2.0 makes me want to be one)
      1. Master Pages
      2. New data controls
      3. Membership, role management, and login controls (it couldn’t get much easier)
      4. Amazing profile support
      5. Site maps
    5. Smart Clients
      1. Amazing improvements to VSTO
      2. Click Once
      3. Very cool designer support
    6. Language and Framework upgrades
      1. There are too many to list (My, Partial Types, and the list goes on)


    For those out there who have been working with the Alphas and the Betas of these products you are probably as excited as I am about all of this.  For those of you who are just getting into this new stuff – take a deep breath – because, here it comes!


    See you at the launch activities.


  • VSTS Process Template Editor - October 31 Release

    Visual Studio Team System Process Template Editor – October 31 Release



    Version 0.5.2131.27160


    As promised, here is the October 31 release of the Process Template Editor.  The focus was on way more validation of the resulting templates


    1. WAY more validation for the Process Template and the Work Items
    2. Ability to work Online for even further validation
    3. Work Item Conditional Rules


    We’re still working on fine tuning many of the features including:

    1. Online WorkItem Editing
    2. SharePoint definition
    3. Better Work Item Form rendering
      1. Type Definition
      2. Initial Work Items
    4. Icons
    5. Work Item Query Editing
    6. Global List Management (online and template files)


    Let me know if you have any problems.