May 2005 - Posts

Available Controls for Team System Work Item fields

If you are looking for a complete list of controls available for use on Work Item form (not all of them documented in extensibility kit docs), here it goes:

ExtendedComboBox
FieldControl
DateTimeControl
HtmlFieldControl
LinksControl
AttachmentsControl
TFStructureControl
WorkItemLogControl

Thanks to Naren Datha for information.

And one more insight from Naren: ExtendedComboBox and FieldControl are actually the same. ExtendedComboBox kept for backward compatibility only.

Team System Work Item Field names

Couple annoying things about Work Item field definition:
  1. Work item name can not contain underscore or other not alpha-numeric characters. Spaces are allowed. Just spent some nice time replacing underscores in Work Item type fields migrated from ClearQuest. CQConverter migration tool did not consider it a problem.
  2. Work item name should be unique. It is probably very logical decision, wich encourage naming consistency. The only problem for now is that I keep bumping into field names predefined by Microsoft (in namespaces like Microsoft.VSTS.Common for example). There is partial list of predefined fields in System namespace in extensibility kit documentation. As far as I know, fields from Microsoft.X namespaces are not documented yet.

ASP.NET tab disappears from IIS MMC Application Properties

When Visual Studio 2005 installed on W2K or Win2003 platform, ASP.NET tab magically disappears from IIS MMC. ASP.NET tab used to set ASP.NET version for specified virtual directory. This behavior was introduced with 8.0.50203.0 (CTP) version and still present in beta2 release.

There is an open bug on this (open by Juan T. Llibre). Please review and vote.

For now if you want to run both ASP.NET 1.X and ASP.NET 2.0 on the same machine, you can use Denis Bauer's ASP.NET Version Switcher

Thanks to Memi Lavi for better solution: Clean registry settings. Worked for mine W2K VS2005 installation

ASP.NET 1.X to ASP.NET 2.0 migration talk

I am going to talk about ASP.NET 1.X to ASP.NET 2.0 migration at "Get Ready to VS2005" Microsoft Israel event.

Topics I am planning for now are:
  • Side-by-Side execution and configuration
  • Automatic conversion and Upgrade Wizard
  • XHTML and client resources issues
  • New Compilation model issues
  • Naming collisions

If anybody can think of other issues/pitfalls related to 1.X to 2.0 migration, I'll be glad to here. Any suggestion is welcome!

Team System Portal Error: "Unable to locate control: ctl00oReportCell"

There is a known issue with TS beta 2. After Team Project creation, when trying to open Project Portal you will receive  IE alert "Unable to locate control: ctl00oReportCell" (one for each Report Web Part). It is not fatal but very annoying error. Amaxo has good explanation how to fix it including download. Nicely done!

Scheduling build in Team System beta 2

Apparently there is no built-in option to schedule build in Team System 2005 beta2.  The only way to do it, is writing external application to invoke build engine and put it on NT scheduler. Good news is that it is pretty simple. See Scheduling Daily Builds thread.

Team System 2005 Beta 2 Extensibility Kit

For those who are already working with VSTS 2005 beta 2 and interested in customization, previous version of Extensibility Kit (1204 CTP) will no longer work with current version of Visual Studio.

New version is available here.

VS 2005 beta cleanup tool

For all of you, who struggling to make Team System 2005 beta 2 work on machines, which already suffered enough from different CTP versions, this tool can help.