Grant Holliday, former Team System MVP, is now working on the VSTS product group on various things but most importantly helping keep the internal Microsoft TFS servers in tip-top shape.  They have the largest known TFS instances in the world so you could imagine it’s got to be tough keeping it up and running well.  Brian Harry posts their usage metrics regularly if you’d like to get an idea of how HUGE it is.

Keeping the performance manageable requires lots of monitoring and looking over the data that gets stored in the activity logging.  Grant has packaged up some of the reports they use internally and provided them to the world.  The download package is available on his blog post.

Personally, I’m really glad that the product group is investing in dogfooding the early builds of the version of TFS that they are working on.  By putting the product under real use and under the load that only Microsoft can generate, we end up with a better product by the time it RTMs.

Thanks again for making this available to the world!

Ed B.

Here are some links to get you started learning and developing on the Azure platform.

Azure Services Platform

Azure SDK downloads

Azure training Kit

PDC recorded sessions

Azure sample application (IssueTracker)

MSDN Azure blog

Ed K.

Well, I have hit my one year mark of not using tobacco products!! Its been extremely hard but well worth the sacrifice. I will not lie to anyone thinking about quitting....I still have cravings but they are not as bad and they do not last as long. The main thing that got me through the first 6 months was "hard candy" by the truck loads (weight gain was present) and family support. After 6 months I was able to manage cravings with exercise and avoiding stressful situations.

Ed K.

From those of you that use the Workgroup edition of Team Foundation Server you might have notice that you cannot use the Build Notification Power Tool since you cannot authenticate to TFS.

Here is what I have done to work around the noted limitation:

"RunAs" to the rescue:

C:\Windows\System32>runas.exe /user:ROSCOE\jbm /netonly "C:\Program Files\Microsoft Team Foundation Server 2008 Power Tools\BuildNotification.exe"

To automate, create yourself a little batch file for startup. Here is a VBS script to automate the entry of the password for RunAs:

dim WshShell,FSO

set WshShell = CreateObject("WScript.Shell")
set WshEnv = WshShell.Environment("Process")

set FSO = CreateObject("Scripting.FileSystemObject")

WshShell.Run("C:\Windows\System32\runas.exe /user:ROSCOE\jbm /netonly" & " {YourInstallPath}\BuildNotification.exe")

Wscript.Sleep 300 ' Wait for window to open

WshShell.AppActivate("C:\Windows\System32\runas.exe")
WshShell.SendKeys "{YourUserPassword}"
WshShell.SendKeys VBCRLF

set WshShell=Nothing
set WshEnv=Nothing
set FSO=Nothing

wscript.quit

[UPDATE]
You can "Connect As" from the GUI; Unfortunately, you will have to do this each time you restart.

Ed K.

I’ve been in the middle of a lot lately and completely forgot to mention Tulsa TechFest 2008!  This will be my third year speaking and interestingly I have the only Team System talk this year.  If you’re around the area be sure to come by to learn more about automating your build & packaging process using Team System.  I’m going to do my Team Build talk that I did earlier this year at the Dallas VSTS User Group but we won’t go into as much depth since we only have 1.5 hours.  Looks like another great year with almost.  Infragistics has been a proud & regular sponsor of this event and I’m honored to have been invited again!

[Update]

Wanted to be sure I posted my slides and then also made the link to the awesome build lifecycle poster done by our friends in South Africa.  Thanks for keeping me honest!

Ed B.

I didn't get to read my RSS feeds yet today but I got a hint to go read them and I discovered that Chuck wrote a nice blog post about volunteer work and me.  I guess the cat's out of the bag now :)  Thanks Chuck for the kudos - I really appreciate it.  I'm looking forward to making a really good use of that time.

There are so many people in the development community that spend countless hours of their volunteer time.  Especially in the VSTS community.  People are working volunteering time:

• developing and supporting open-source projects & tools,
• speaking at events and conferences (this takes a considerable amount of time to prepare for,)
• leading local user groups,
• writing blog posts, technical articles, & books,
• answering community questions in the MSDN Forums,
• giving feedback, enhancement requests, & reporting problems of Microsoft products to improve them, and
• all of the other ways people volunteer time that I can't even begin to think of.

I personally know several people (and more) who really focus on trying to make the entire development community better off with these time & knowledge contributions.  (Infragistics as a company has been really supportive in all of our efforts to help the community.) I hope you get as much out of it as I do from learning from everyone.  Microsoft has done a great job in recognizing those individuals by creating the Most Valuable Professional (MVP) award.  I'm honored to have been awarded this award earlier this year.

I've really not been able to blog as much as I have liked to or participating in the MSDN Forums answering people's questions.  I have focused the volunteer time that I have had in other areas.  I had a really great time at the MVP Summit earlier this year and came back with so many different ideas.  I really love the VSTS MVP & Champs group - truly a great group of professionals!  This brings me to my idea for this year.

I feel like I haven't had time this year to really provide anything meaningful to the community.  So, I want to dedicate a work week and do something meaningful for the VSTS community.  There are plenty of places that we could all use help so I think that would be something meaningful and useful.  I'm planning on doing this time locally in Redmond so that if I need background information on a project, I can get it quickly.  I need to meet with some people about Infragistics stuff and really take some vacation time in that area (since it is so beautiful) so I think it's beneficial to be local during that week.

What should I work on?

Chuck mentioned a few ideas that we have so far but the one I personally love is being able to release the gigantic amount of work that Microsoft has done with their internal process templates & reports.  Have you seen them?  They are awesome!  Reports are so tricky to do and take a good chunk of time to be done correctly.  The Microsoft internal reports need to be scrubbed for external consumption which is my initial idea for volunteer work.

Or should I work on a productivity tool?

Don't let me taint your opinions though.  What do you want/need that would be valuable for VSTS?  Go to Chuck's blog post and give us suggestions about what you would like to see me work on.  No car washing or details though :) unless it's for a good charity organization then I'll consider it.

Ed B.

So, I came across something pretty interesting when I was making a work item query today that I've wondered for a while.  I can't believe I just came across it today.

OK - Just for some background on what I was trying to do:  I wanted to get a team query made that returned all of the bugs for my team.  The only problem is that our department supports all of our products for mainly builds & installers (among other things) and it causes the Area Paths that we look at to be pretty much all over our TFS server.  Usually you would just want all the bugs for a particular product and you can use the UNDER operator for the Area Path field.  I need to use multiple condition clauses using the UNDER operator.  I knew that the Work Item Query Language (WIQL) had a way for putting parenthesis around the conditionals in the WHERE clause.  (The WIQL syntax is very similar to T-SQL if you haven't ever seen it before.)  For example, here's part of a sample WIQL query that I was going after....

SELECT [System.Id], (Other Fields) FROM WorkItems WHERE [System.WorkItemType] = 'Bug'  AND  [System.State] <> 'Closed'  AND  ([System.AreaPath] UNDER 'NetAdvantage\.NET\Installers'  OR  [System.AreaPath] UNDER 'NetAdvantage\.NET\ASP.NET\Builds'  OR  [System.AreaPath] UNDER 'NetAdvantage\.NET\WinForms\Builds'  OR  [System.AreaPath] UNDER 'NetAdvantage\WPF\Builds'  OR  [System.AreaPath] UNDER 'NetAdvantage\WPF\Installers'  OR  [System.AreaPath] UNDER 'TestAdvantage\QTP\WinForms\Builds'  OR  [System.AreaPath] UNDER 'TestAdvantage\QTP\WinForms\Installers'  OR  [System.AreaPath] UNDER 'TestAdvantage\RFT\WinForms\Builds'  OR  [System.AreaPath] UNDER 'TestAdvantage\RFT\WinForms\Installers')

My problem was - how do I put parenthesis in the query using the Work Item Query Editor? (UI in Visual Studio)

However, I remember reading Brian's post yesterday about the new Alerts Editor (which by the way is totally awesome and immediately adds value to the product without waiting for the next major release) and thought, I wonder how they did that in the UI with the alerts XPath queries because I know you can't get very good alerts without the ability to group the XPath query conditionals.  Let me steal an image from Brian's post with a little editing showing off a grouping of condition clauses:

I thought to myself, hmmmm... that grid looks pretty similar to WIQ Editor grid that exists today in Team Explorer 2008 and started searching everywhere for the "group" tool button (since there is not a toolbar above the grid.)  I found it.  It's in the context menu whenever you select multiple rows.  Seriously, I can't believe I haven't ever seen it before.  I guess I don't usually write very complex work item queries :)

Have fun writing some useful queries for yourself and your team now!

Ed B.

Speaking of Team System, I found out last week that I have been officially inducted into the Team System MVP group.  Earlier this year, I was awarded as an MVP in the Client Application Development competency.  Don't get me wrong, I still love WPF & Silverlight development and will continue to be involved in that community in the future.  I'm even working on finishing up the technical editing of a Silverlight 2 book right this minute. Or actually I'm procrastinating writing blog posts :)

Being part of the Team System MVP group, I'm really joining one of the most awesome groups ever.  I spent all of my time earlier this year at the MVP Summit at all of the Team System sessions and they truly are one of the best product teams at Microsoft.  They truly value our feedback and the Team System MVPs really love and care for the product just as much and want to see it grow by leaps and bounds.  And when I say love and care for the product, you don't even understand! :) This is definitely a good fit and I'm honored to officially join the group.  So when do I get to learn the "secret handshake?"

Ed B.

Fellow Team System MVP Mike Azocar has announced an awesome new contest to stir up the Team System tools ecoystem.  There are some really cool prizes so far including a free license for Microsoft Visual Studio Team Suite 2008 w/ MSDN Premium subscription and there are more donated prizes coming...  Get the full details at his blog post:  Want to be famous- Enter the Coolest Team System Gadget Contest!

Have you created a useful gadget for Team System? Do you have one in mind? I am looking for the coolest community built tool for VSTS. It can be something for TFS, for Visual Studio, or something that is stand alone. The winner will receive a one year subscription to MSDN with Team Suite!

To enter, submit a screen cast (up to 3 minutes long) which tells everyone why your gadget is the coolest and the source code. All submissions will be released to the public as free source to use and enjoy (with you getting all the credit of course). Videos will also be made available to the public to help make you famous! This should be something new (i.e. not on Codeplex or previously released) and not something repackaged. Submissions accepted up until August 31st 2008. Winner will be announced September 15th 2008.

Judges will be Mike Azocar, Martin Woodward, and I so this is going to be a lot of fun!

Ed B.

I'll be speaking on July 1, 2008 at the Dallas Visual Studio Team System User Group. Starts at 6 PM.  This is going to be a really exciting session for me personally and I love that we have a big block of time to get into some really fun Team Build details.  I think we are meeting at the Notion Solutions office in Irving for the July meeting but I'll double-check and update if there is a change.

Here are a few topics that I'll make sure we talk about:

• New Features for Team Build 2008
• Fun Stuff around Builds at Infragistics
• Build Notification Power Tool
• Building Java applications using Team Build & TeamPrise - (This blows people's minds away)
• Building Installers using Wix
• New Changes in TFS 2008 Service Pack 1 for Team Build
• If time, Extensibility with the Team Build API

Be sure to sign up on the user group website to get updates and the RSVP link whenever it gets sent out.

Ed B.

Our team has been kept extremely busy lately with our new responsibilities.  What does the Release Engineering team do exactly?  Along with creating builds and installers for ALL of our products, we now have responsibility of Team Foundation Server Operations, and the entire development lifecycle of internal productivity tools that we call the "Internal Tools Suite."  So to sum it up, if it has to do with automation or the release process, it's us :)  We need some help (so I can get around to doing some blog posts again haha.)

Here's the positions we have open for the department:

• Software Engineer in Release II, Princeton, New Jersey
• Software Engineer in Release I, Sofia, Bulgaria

Come join our team! It's been extremely exciting lately with what we're doing internally at Infragistics.  Contact me if you're interested:  ed AT infragistics DOT com

Ed B.

There is a new book about VSX out from Wrox called “Professional Visual Studio Extensibility” and looks pretty promising if you are first starting out to learn add-ins and VSPackages.  It's actually the first one that I've seen get released so I hope it does well.  VSX is a topic that I have a keen interest in.

• A quick overview of Visual Studio Shell and Domain-Specific Languages Tools
• Techniques for creating, debugging, testing, and deploying your add-ins
• Ways to work with user interface elements, Windows Forms, and controls via code in your add-ins
• Steps for extending Visual Studio functionality using VSPackages
• Tips for writing and managing code snippets to make your coding process easier
• Using Visual Studio templates to save time when writing code for common projects
• How to use MSBuild to write custom builds for Visual Studio and .NET applications
• New techniques for recording, developing, debugging, deploying, and running macros

Ed B.

It's finally available!  Seriously - this CTP has quite a bit of features that they have added and you can start to see that VSTS is and will continue to be a strong if not the best ALM offering.  The new features are added to Head over to Jeff Beehler's blog post to find out more details of what has been added...

I haven't picked a favorite feature just yet :)  The three I just really like the most across the whole offering:

• New Team Build System based on Windows Workflow Foundation
• Historical Debugging (this will really help with the Debug and Repro scenarios)
• Great Test Case Management System

Here's a list of all the new features!

Architecture Edition

• Exploring the existing code structure
• Designing process flow as activities
• Designing user interactions with systems
• Designing system functionality as components
• Visualizing and designing types in systems
• Visualizing and designing interaction sequences in systems

Development Edition

• Simplify Code Analysis rule selection with rule sets
• Find and fix a bug using the historical debugger
• Identify the test impact of code changes
• Find a bug on a separate machine using the standalone debugger

Database Edition

• Building and using an off-line representation of your operational database as a “sandbox” development environment.
• Using Data Generation to custom-build data for testing your database application.
• Making and unit-testing schema and code changes in an off-line environment.
• Performing static code analysis of your programmability objects.

Test Edition

• Planning a testing effort
• Executing manual test cases
• Verify the fix
• Automate a manual test and add validation.

Team Foundation Server

• Managing an Agile schedule
• Easier reporting from Excel
• Managing features with the CMMI Process
• A new Add Files to Source Control wizard and support for drag and drop from Windows Explorer to Source Control Explorer
• An enhanced, non-modal conflict resolution experience, integrated into the pending changes tool window
• A new history view that shows labels applied to a file as well as how changes were merged across branches
• A new automated build system built on Windows Workflow Foundation, featuring dynamic build machine allocation from a machine pool and distributed build functionality
• Rollback for a check in (currently only available at the command line)
• Many Source Control Explorer usability enhancements

Be sure to head to their Connect site with your feedback!

Ed B.

When creating a transition between states you may want to use a "Server" level security group for the "For" and/or "Not". Taking a first stab at doing this you will probably do as the screen shot below.

When you go to validate this you will get the error shown in the screen shot below. You might even bang your head a couple times trying to figure out what the deal is. :) TF26171

The correct way to specify a SERVER security group is shown in the screen shot below

Ed K.

I'm really excited because the last three days I've been in Redmond, WA attending the TAP briefing for the next version of Visual Studio Team System code named "Rosario."  All I can say is WOW - I'm completely impressed with the work that Microsoft has done and the amount of effort they are making into making the next version of Team System be absolutely awesome.

A lot of big announcements were made and we received a lot of insight into the future.  However, I'm not allowed to say anything just yet about any of it since we were all under a Non-Disclosure Agreement (NDA)  I'm reviewing the latest bits and going to start several blog articles about the multitude of amazing features and as soon as I am able to talk about it I will.  (By the way there are early bits available in the November CTP already that you can download using the Rosario link above!)

It was great meeting with the other VSTS Champs in person and putting faces with names.  Truly a great event and I really got the impression that the VSTS product team members were genuinely interested in how we felt about the product and our opinions about what we were being shown.  That kind of commitment to receiving feedback from real end users really shows in the quality of their product.

All I can say is that I can't wait until we receive the final bits and are using it in production!

Ed B.

So here at Infragistics we're truly a global company now which makes life as a TFS Administrator very "interesting" for sure!  Everyone is working around the clock and things can go wrong pretty much 24-7.  Oh well - I'm used to it already :)

If you didn't know, last week Microsoft announced that all of the localized versions of Team System Web Access (TSWA) had been finished and available for download.  This was great because we needed a couple of them for internal use. The only problem I found was that you can't install more than one version of TSWA on the same machine.  That's no fun :(

Thankfully Hakan came to my rescue and gave me a few steps to try and they definitely worked out for me.  I did everything on a separate virtual machine, gathered all of the files I needed, and then copied them to the TSWA web server. 

Disclaimer:  If you're going to follow the steps be mindful that this is completely unsupported by Microsoft.

1. Install <localized version>
2. Copy the files to C:\TSWA\<localized version code>
3. Uninstall <localized version>
4. (Repeat for all languages)
5. Manually create web sites in IIS to point to each of the different languages
• Make sure each TSWA instance uses a different IIS AppPool
• Make sure each TSWA instance points to a different cachedir

There you go!  Also, it might be helpful to use host headers to help users out with discovering their localized versions of TSWA.  This allows you to use port 80 as well instead of the usual default of 8090.  For example:

• English - tfsweb.[your domain]
• Japanese - tfsweb-jp.[your domain]
• German - tfsweb-de.[your domain]
• etc.

Ed B.

It's available now on MSDN Subscriber Downloads.  It's only available on the front of the Subscriptions site for right now.  It may not show up immediately so you might want to log off of your Windows Live ID and log back in while you're on the same page.

Ed B.

Brian Harry on eScrum TFS 2008 compatibility.

eScrum and TFS 2008

*Sorry folks this blog post is mainly a book mark for me so I can google my brain later.

Ed K.

I was just reminded this morning by an old colleague that Ed K. and I have been slacking tremendously since we haven't had any blog posts since November :)  I want to wish everyone a happy new year and share some news.  Last week, I moved back to Dallas and will be working remotely from home.  It's new for me so I'm still trying to get into the groove of things.  Scott Hanselman's latest posts about being a remote worker have been extremely interesting to me.

It's been a little hectic in the last few weeks.  I needed to wrap a few things up before I went on vacation at the office.  Also, we had our final NJ .NET User's Group meeting for the year which turned out to be terrific.  Since it's a new year, we also had announced a new leader - Jess Chadwick.  It has been a privilege to serve as a leader of the group for 2007.   I really want to thank Jess, Tony, Ambrose, Kathleen, and Peter for the help during the year in leading the group.  I'm looking forward to rejoining the Dallas .NET community and also the newly formed Dallas VSTS Users Group (How exciting!)

From there, there was:  packing, cleaning, movers picking up, cleaning, driving, getting the new place, movers dropping off, unpacking, getting new furniture, setting up the new office, having out-of-town guests, whew... and getting ready to host a party!

After waking up from a very long but extremely fun night on New Year's Eve (which ended up being my housewarming party as well since all of my friends were in town,) I was surprised to find an e-mail in my inbox:

Congratulations! We are pleased to present you with the 2008 Microsoft® MVP Award!

Oh I was/still am pretty excited! :)  It's exciting to be working at Infragistics for many reasons.  They have been the most supportive company that I have worked for when it comes to being involved in the developer community which is one of the primary reasons I came aboard a year ago.  Describing Infragistics as "community-friendly" would be putting it mildly!  There's a total of SEVEN MVPs now at Infragistics which is a testament to the quality of people that I have the privilege to work with every day.  We really do have the best people in every department around the company.

There are so many people who really have been extremely helpful to me.  I want to specifically thank Ambrose for his mentorship as my coach for the majority of 2007.  He has been very influential in my career and cared about my professional growth.  Thank you!  So many people deserve Kudos:  Ed K., Jess, Tony, Jason B., Peter, Grant, Kathleen, Devin, Josh, Tim, Caleb, Omar, Fraser, Jason T., Chuck, Mel

I'm still working on getting my profile to get it all set up with my information so for now it's a work in progress:  My MVP Profile

All in all, I'm looking forward to the new year and what exciting things are in store both at Infragistics and with my continued involvement with the developer community.  It's going to be an awesome year!

Ed B.

If you happen to use Dotfuscator by PreEmptive Solutions then you have probably wondered how to integrate this into your automated Team Builds.  They happen to include an MSBuild task for calling the proper command-line functions but don't have much documentation about this feature.

Background Obfuscation Information:  In general, obfuscation prevents reverse engineering of your software by using different techniques to make the MSIL of your .NET compiled application less understandable.  Several different companies use many techniques for doing this including: string encryption, renaming of symbols, control flow manipulation, etc.  If you've ever used Reflector for .NET you know how easy it is to look at reverse-engineered "source code" for a .NET application.

• Start by putting your Dotfuscator configuration file in the folder that contains your team build script (i.e. TFSBuild.proj) and it to source control.
• Open up your team build script and edit it.  (Be sure to check it out first.)
• Start by adding a reference to the proper custom targets file that is provided.  You should have a Dotfuscator Build Machine license installed on the TFS Build Server(s.)  If you got the wrong license version, just ask them for upgrade pricing.
  
  <Import Project="$(MSBuildExtensionsPath)\PreEmptive\Dotfuscator\4.0\PreEmptive.Dotfuscator.Targets" />

• Next, add a section for the Dotfuscator Properties you will need.  You'll notice we have a keys directory that gets pulled down from source control during the build process.  We keep our strong name key in this direcotry and the keydir directory property is for resigning the assemblies after the obfuscation is complete.
  
    <!-- Properties for Dotfuscate Task-->
    <PropertyGroup>
      <ConfigPath>$(SolutionRoot)\..\BuildType\Dotfuscator.Configuration.xml</ConfigPath>
      <InputPath>$(SolutionRoot)\..\Binaries\Release</InputPath>
    </PropertyGroup>
    <PropertyGroup>
      <DotfuscatorProperties>
        <targetdir>$(InputPath)</targetdir>
        <keydir>$(SolutionRoot)\Keys</keydir>
      </DotfuscatorProperties>
    </PropertyGroup>
    <ItemGroup>
      <InputAssembly Include="$(InputPath)\*.dll;$(InputPath)\*.exe" Exclude="$(InputPath)\*.vshost.exe"/>
    </ItemGroup>  

• Finally, customize the AfterCompile target by adding the Dotfuscate task with appropriate property settings.  See more information about Customizable Team Foundation Build Targets.
  
    <Target Name="AfterCompile">
      <!-- Perform obfuscation steps after assemblies are compiled.-->
      <Dotfuscate InputAssemblies="@(InputAssembly)" Properties="$(DotfuscatorProperties)" ConfigPath="$(ConfigPath)">
        <Output TaskParameter="MappingFile" ItemName="DotfuscatorMappingFile"/>
        <Output TaskParameter="ReportFiles" ItemName="DotfuscatorReportFiles"/>
        <Output TaskParameter="OutputAssemblies" ItemName="DotfuscatedAssemblies"/>
        <Output TaskParameter="SatelliteAssemblies" ItemName="DotfuscatedSatelliteAssemblies"/>
        <Output TaskParameter="DebugSymbols" ItemName="DotfuscatedDebugSymbols"/>
      </Dotfuscate>
    </Target>
  
• Next, take some time to edit your Dotfuscator configuration file.  Notice the properties I am using in my sample project below and what is being set in the Dotfuscator properties collection in the Team Build script above.  Basically, I have just cleared the property values out to make sure that the MSBuild task populates them correctly.
  
  <?xml version="1.0" encoding="utf-8" standalone="no"?>
  <!DOCTYPE dotfuscator SYSTEM"http://www.preemptive.com/dotfuscator/dtd/dotfuscator_v2.1.dtd">
  <dotfuscator version="2.1">
    <!--This is application generated code. Do not edit manually.-->
    <propertylist>
      <property name="targetdir" value="" />
      <property name="keydir" value="" />
    </propertylist>
    <global>
      <option>verbose</option>
    </global>
    <input>
      <asmlist>
        <inputassembly>
          <option>library</option>
          <file dir="${targetdir}" name="Shared.Library.dll" />
        </inputassembly>
      </asmlist>
    </input>
    <output>
      <file dir="${targetdir}\Dotfuscated" />
    </output>
    <tempdir>
      <file dir="${targetdir}\Dotfuscated" />
    </tempdir>
    <renaming>
      <!--<mapping>
        <mapoutput overwrite="false">
          <file dir="${targetdir}\Dotfuscated" name="DotfuscatorMapFile-KeepSecure.xml" />
        </mapoutput>
      </mapping>-->
    </renaming>
    <controlflow level="high" />
    <stringencrypt>
      <includelist>
        <assembly>
          <file dir="${targetdir}" name="Shared.Library.dll" />
        </assembly>
      </includelist>
    </stringencrypt>
    <signing>
      <resign>
        <option>dontuseattributes</option>
        <key>
          <file dir="${keydir}" name="StrongName.key" />
        </key>
      </resign>
    </signing>
  </dotfuscator>
   
• That's it.  Finally, just customize it to your heart's content!

Feel free to let me know if I can improve this in any way!  I'm always looking to efficiently refactor our Team Build scripts.

Ed B.