Sorry this post is mainly for me again :(

I am building some tools to help manage the complexities that come along with Localizing an enterprise application. I will post the source(s) when I get a chance to clean everything up :)

Neutral and Specific codes for localization

Ed K.

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.

I'm excited to announce that we have finally released a free tool to help you visualize resource usage in your WPF applications.  Kudos to the team on a job well done!

Pistachio helps you by:

• Seeing what resources are being used.
• Finding unused resources.
• Displaying the types of resources being used.
• Filtering, Sorting, etc.
• Cool Visualizations of Usage

If you were at either of my talks at Boston ReMix or Tulsa Tech Fest you got a pre-release preview but now it's all ready for you to use!  Please let us know if you have any suggestions or problems while using.  There are several more features being planned so let us know what's important to you.

DOWNLOAD HERE:  Pistachio - WPF Resource Visualizer

Ed B.

Ever since I started at Infragistics, I had been working in the User Experience Group (under the Evangelism umbrella) primarily with WPF & WinForms.  As some of you know, I wasn't too fond with WPF at the beginning :) but now I love it.  [Shameless Plug:  Have you checked out Tangerine?  See my blog post about it.]

I have taken a new position now as what is usually referred to as the Configuration Manager (HR Title:  Configuration and Process Improvement Engineer.)

As some of you know, I have been working with Team Foundation Server since pre-beginning (is that a word?) like during the Betas.  [Strolls down memory lane... Anyone remember the Beta 2 to Beta 3 upgrade? whew... Ed K. remembers that day with the 3-hour phone call from the TFS Product Team.  Those were the days. I got a cool TFS All Stars shirt from it though!]  I digress.  Infragistics has decided to adopt TFS and planning to migrate pretty much all of our separate systems to it.  So, that's what I'm doing now in the Engineering department!  Although I'll be missing doing WPF and Evangelism work, I'm pretty excited about getting to do TFS stuff full-time.

If you were at Grant and I's talk at Boston ReMix or my talk at Tulsa Tech Fest, you got the preview of a community WPF application that we're working on to gather data from TFS and replace our Release Status Wall.  It's basically an application to visualize your release process.  As soon as we get something ready to preview, I'll definitely post up on here.  So I get to put my love of both WPF and TFS together!  Grant's a God-send when it comes to making applications look great. I'm really blessed to be working for a company that has a dedicated Visual Design team... We have 5 dedicated Visual Designers now... wow.

Another one of my goals with our new system of tracking development data is to provide more transparency to our customers in regard to feature tracking, bugs, etc.  I think it's important (as a previous customer) to be able to have that kind of transparency.  I'm thinking something along the line of Microsoft's Connect website.

So I look forward to being able to talk more about TFS and coming out with some exciting tools and information.  Don't worry, I still do WPF development too so you'll still see me from time to time blogging about it and speaking.  I just finished up a WPF magazine article yesterday even :)

BTW... I'll be in DevConnections next week in Las Vegas doing some WPF Evangelism stuff so be sure to hit me up if you'll be in town!

Ed B.

I don't know how I ever missed it but I was shocked to find that I could not restrict users from branching and merging in TFS Version Control.  Ahhhhhh!!!!

The only security privileges (for Version Control) that are available are:

• Read
• Check out (branching, merging, and other similar pending changes fall into this category)
• Check in
• Label
• Lock
• Revise other users' changes
• Unlock other users' changes
• Administer labels
• Manipulate security settings
• Check in other users' changes

If you want more information about the specifics for Version Control privileges, check out MSDN at:  http://msdn2.microsoft.com/en-us/library/ms252587(VS.80).aspx

If you are facing this same issue and believe that it should be a feature in the product, help out by voting on the feature suggestion on Visual Studio Connect:  https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=307874

Ed B.

So there is a huge problem with uninstalling the TFS Power Tools if you have them installed on Windows Vista.  This becomes particularly a problem when you want to upgrade the TFS Power Tools (which I was trying to do to the version just released a few weeks ago.)

If you try to uninstall the regular way, you get all sorts of errors like:

Error 1722. There is a problem with this windows Installer package. A program run as part of the setup did not finish as expected. Contact your...

Seriously - it sucks.  I even got fed up and finally decided to rebuild my machine at work (this particular uninstall experience wasn't the only reason for rebuilding my work laptop but definitely was the tipping point!) :)

Anyhow, just to save you a lot of problems, open up a command prompt as an Administrator and run:

msiexec /x {C802488F-CB5F-48BE-BBD2-0C0F9E290E63}

Click "Yes" to the next prompt and you should have a clean uninstall!

Ed B.

VS 2008 has added a new feature called Code Metrics (CM). Code Metrics is a way to produce actionable information on a project or solution. When you generate CM on your code it produces such things as Maintainability Index, Cyclomatic Complexity, Class Coupling, Inheritance depth and lines of code.

Here is a brief description of each:
Cyclomatic Complexity: How many paths of execution are in your code. i.e. Enter a Method, That's 1, Hit an If, That's 2, Hit an Else, That's 3. This has a Cyclomatic complexity of 3. Here is more robust definition.
Class Coupling: Indicates how many other classes relate to this class
Inheritance depth: The level of inheritance
Lines of code: Self explanatory, everyone's favorite
Maintainability Index: An aggregate of the above metrics.

Each of these are shown at the assembly level then it allows you to drill down to the namespace, class and method level.

Why is this so cool? Being able to produce and show these metrics allows you to better manage existing code and produce more manageable new code, which in turn pushes you and your team to code to better standards. These metrics are actionable, meaning they enable you to do something with your code by visually displaying the information and giving you the ability to actually assign a work item right from the Code Metrics result window and attach the information to it as well. 

This is only one tool in the suite of tools within VS 2008 that will enable and guide you to produce better, more secure and performant code. Harness the power of them all!

The Code Metrics result window; user adding a work item based off metrics: