Brian Harry recently posted more information about TFS installation expirations and upgrades. I must admit that this applied to us since we installed the workgroup edition and figured out what had happened while adding our sixth registered user, ugghhh. It was not an exciting time. We are currently in the process of upgrading from TFS workgroup version to the full TFS version, and I'm really hoping that this will work out ok. From the description in Brian's blog post I doubt that we will have any issues (although he was talking about moving from the TFS trial install to the full TFS version).

Also included in the post was an attached application which, when ran on the TFS server, will display that TFS installation Version. Also, you can detect your version without this application by looking opening your Registry Editor. You can find more information on what to look for at Rob Caron's Blog post.

Team Foundation Server Version Detection Screenshot:

Click here to download TFSVersionDetection or you can visit Brian Harry's blog post to download.

There was a recent TFS Version Control Blog post which asked the community for feedback regarding TFS Version Control Check-In policies. The feedback questions were as follows:

1. Would you like us to release a check-in policy pack together with some best practices and ship that out of band?
2. If we do decide to do this then the next question becomes which policies are customers writing themselves that we can standardize and put in the pack?
3. Which policies would customers like to see as examples?

Please visit reply to the post so that we can hopefully convince the TFS Version Control team to release a some standard check-in policies.

The TFS Version Control Blog is ran by Mario Rodriguez who is a program manager on TFS Version Control. Keep that in mind when you post your feedback comments. I know that I would personally love to see a standard check-in policy pack which would handle the most common policies. Due to the fact that these policies are assigned on the server, but need to be enforced on the client, has been somewhat of an issue for myself. Out of curiosity...Is there any standard approach to making these policies. I do understand that we need to override the methods from the PolicyBase class, but is there a recommended way to deploy these policies to all of the clients?

It appears the channel9 will be adding an additional VSTS tag for all Visual Studio Team System releated content.

We recently started tagging new Visual Studio Team System-related content on Channel 9 with a VSTS tag to make them easier to discover. I also just finished tagging all of the older Team System-related content as well. There were several great videos out there, including some that I had never even seen before!

Brian Keller's blog post provides some examples of some videos which can already be found on Channel9. Samples included Application Designer Videos, Code Profiler and Source Control Management. Also there are a few videos which are related to TFS third parties and Microsoft Research Project tools.

View all VSTS tagged content @ channel9.msdn.com

A new version of dasBlog was released a few weeks ago. I must admit, that I downloaded and installed within minutes of seeing Scott Hanselman's blog post. When I initally started this blog I had a really hard time deciding which platform to use...should I use the more populare WordPress, should I try and get Community Server up and going, it was kind of hard to decide at that time. It wasn't until this release that I fully stood behind my inital decision to use dasBlog.

My favorite features include:

• Support for Google Sitemaps - The google webmaster tools and their analytics tools really make maintaining and running a site that much more fun. I think it was especially important to support google sitemaps since the content on our blogs are constantly changing. Note: The location to reference for your google sitemap can be found at [YourBlogDomain]/googlesitemap.ashx
• Better support for Windows Live Writer - Im assuming that the file uploading issues were fixed. Although I already configured LiveWriter to FTP all of my files up the server when needed.

I would also like to mention that the upgrad from 1.8 to 1.9 was a piece of cake. I just merged the web.config files and pushed the new files to the server.

More Information:

Scott Hanselman on dasBlog 1.9

Scott Hanselman on Google Sitemaps

Google Webmaster Tools

Google Analytics

dasBlog 1.9 upgrade information

Wow. Component Art has released one of the most impressive displays of AJAX enabled controls. I'm really getting anxious for Atlas to get out the door because I can't wait for the day that ASP.NET sites stop being the ugly red-headed step child of dynamic websites. Obviously that's an overstatement, but with this great release of Atlas I think we're all going to be blown away both by the third party control vendors as well as the home grown sites too.

Other AJAX Enabled control suites:

• Telerik
• Infragistics
• Of course the Atlas Control Kit

One of my most favorite features with TFS Version Control and Team Foundation Power Toys has to offer is Annotate. With annotate every single line of source code labeled with:

1. The user who made the last changes on each individual line of code
2. The changeset associated with the annotated section
3. The date of the changeset
4. A right click menu which gives you acces to - the changeset details, the history of the file, and the ability to annotate an the previous changeset version.

TFS Annotate Screenshot

Click here to download the latest version of TFS Power Toys

Brain Harry gives us an insight into a few of the changes that we should expect in the next refinement of Annotate.

Brian Harry has provided a list of the Bug fixes we should expect for the Team Foundation Server Service Pack 1. The fix I was most excited about was the common MS Project issue where resources could not be mapped to TFS because a comma was being used the separator in our domain accounts.

Yeah now I can change back my List separator from the ";" to the ",". (Not that I ever noticed any issues from having this setting).

In regard to my previous post on tracing sql statemens generated by llblgen, it turns out that someone has developed a more useful method for tracing LLBLGen Pro 2 by extending the internal partial class and modifying the output so that you can copy and past the SQL statements written to the Output window into Sql Management Studio or Sql Query Analyzer.

Click here to read the full blog entry @ RightHand blogs

The following information is extremely helpful if you find a need to view all of the SQL statements which LLBLGen Pro is generating while executing your project. Sitting back and letting LLBL Gen act like a magical bridge between your objects and your database, but sometimes you really need to know whats going. Perhaps the biggest reason why I decided to dig a little deeper stemmed from the fact that we were on a project with huge scalability concerns.

Add the following to your web.config file following the <system.web> section.

<system.diagnostics>

    <switches>

        <add name="SqlServerDQE" value="4" />

        <add name="AccessDQE" value="4" />

        <add name="OracleDQE" value="4" />

        <add name="FirebirdDQE" value="4" />

        <add name="MySqlDQE" value="4" />

        <add name="DB2DQE" value="4" />

        <add name="PostgeSqlDQE" value="4" />

        <add name="ORMGeneral" value="0" />

        <add name="ORMStateManagement" value="0" />

        <add name="ORMPersistenceExecution" value="3" />

    </switches>

</system.diagnostics>

Watch the Output menu to see what statements are being built and executed by the SqlServer Dynamic Query Engine

Sample output:

Method Exit: CreateSelectDQ
Method Exit: CreatePagingSelectDQ: no paging.
Method Enter: DaoBase.ExecuteMultiRowRetrievalQuery
Method Exit: DaoBase.ExecuteMultiRowRetrievalQuery
Method Exit: DaoBase.PerformGetMultiAction
Method Enter: CreateRowCountDQ
Method Enter: CreateSelectDQ
Method Enter: CreateSelectDQ
Generated Sql query:
Query: SELECT [TableName].[dbo].[Link].[ID] AS [Id], [TableName].[dbo].[Link].[DisplayName], [TableName].[dbo].[Link].[URL] AS [Url], [TableName].[dbo].[Link].[Description], [TableName].[dbo].[Link].[CategoryID] AS [CategoryId] FROM [TableName].[dbo].[Link]

Method Exit: CreateSelectDQ
Generated Sql query:
Query: SELECT COUNT(*) AS NumberOfRows FROM (SELECT [TableName].[dbo].[Link].[ID] AS [Id], [TableName].[dbo].[Link].[DisplayName], [TableName].[dbo].[Link].[URL] AS [Url], [TableName].[dbo].[Link].[Description], [TableName].[dbo].[Link].[CategoryID] AS [CategoryId] FROM [TableName].[dbo].[Link] ) TmpResult

Method Exit: CreateRowCountDQ
Method Enter: DaoBase.ExecuteScalarQuery
Method Exit: DaoBase.ExecuteScalarQuery
Method Enter: DaoBase.PerformGetMultiAction
Method Enter: CreatePagingSelectDQ
Method Enter: CreateSelectDQ
Method Enter: CreateSelectDQ
Generated Sql query:
Query: SELECT [TableName].[dbo].[Link].[ID] AS [Id], [TableName].[dbo].[Link].[DisplayName], [TableName].[dbo].[Link].[URL] AS [Url], [VirginiaAgencyRedesign].[dbo].[Link].[Description], [TableName].[dbo].[Link].[CategoryID] AS [CategoryId] FROM [TableName].[dbo].[Link] ORDER BY [TableName].[dbo].[Link].[DisplayName] ASC

Method Exit: CreateSelectDQ
Generated Sql query:
Query: SELECT TOP 10 [TableName].[dbo].[Link].[ID] AS [Id], [TableName].[dbo].[Link].[DisplayName], [TableName].[dbo].[Link].[URL] AS [Url], [TableName].[dbo].[Link].[Description], [TableName].[dbo].[Link].[CategoryID] AS [CategoryId] FROM [TableName].[dbo].[Link] ORDER BY [TableName].[dbo].[Link].[DisplayName] ASC

For some reason we started getting the error TF42026 when we attempted to execute our builds. I found this great blog post from Tom Wisnowski which gave a step by step checklist of things to check in order to resolve the issue.

Turns out our this error was being caused from the fact that our Team Build Service was not running.

2. Make sure the Team Build Service is running. Open the services MMC snapin and look for Team Build Service. Make sure the service is running. Also note the account that the service runs as; you will need it for the next step

This may be kind of late in the game to post about a feature which was probably discussed a while ago, but I thought that it would be worth mentioning anyway. Turns out the Microsoft Word 2007 will support blog publishing. I think its great that Microsoft has finally decided to start supporting many of the new "cooler" web features like RSS and Blogging.

Check out Joe Friend's Blog Post for more information.

I stumbled across a very startling blog post by Paul Wilson while reading my feeds today. It turns out that VS2003 will not be supported in Vista and VS2005 is not yet completely supported. I guess I was naive in assuming that both would work fine on the new OS but apparently there are going to be some issues. Im not sure how this will effect my move from XP @ home, but Im absolutely positive that most of our offices are not going to make the switch in a quite a long time.

Check out Paul's blog post

It is interesting to read all of the heated comments in reference to his post.

One of the things that I have noticed about LLBLGen Pro Version 2.0 is that, post installation, the LLBLGenProDataSource control is not added to your control. In my opnion one of the most important additions to the second version for LLBL is the fact that it supports the ObjectDataSource control model, but the control is only useful in your organization if people use it in development.

The following is a summary of how to add the DataSource control to your Toolbox:

1 .Right click toolbar and choose items. (Loading the choose items dialog may take a few moments)

2. On the choose items dialog click Browse

3.Locate the SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll and select open.

4. The choose items list has now been updated.

Sort the list by name and check the box next to LLBLGenProDataSource. (note both of the Datasources will select automatically).

Select OK and view the new items on your toolbar.

It turns out that we have installed the TFS Workgroup edition which translates to the fact that we can have a maximum of 5 registered users on our TFS environment. I guess I should have done a little more research into the licensing issues involved with our MSDN subscriptions but it was such an interesting opportunity to:
1. Install TFS and get it up and running with all of its individual components.
2. Convince our department that a move toward this technology would be a step in the right direction.
3. Gain access to a pilot project which would be used as both a model for future projects and a platform for learning all of the ins-and-outs of using TFS throughout the entire lifecycle of a software product.

From here, we are going to have to look at the different licensing options and choose the best option for out team. The one biggest concern that I have is that the workgroup edition will not be updateable.

More info:

Don't Install Team Foundation Server Workgroup Edition!!!
MSDN Subscriptions Chart
Rick LaPlante's WebLog Post
Eric Hammersley's WebLog Post
Rob Caron's WebLog Post
Team System Licensing Whitepaper
How to upgrade TFS Workgroup Edition