I've posted about this before, however, it's so important I'll repost.  If you're trying to create a listener web service for TFS events, don't start from scratch!  Use Howard van Rooijen's VS2005 template.  It will create the web services, along with the appropriate signatures, as well as convert the events to an object, so that you can effectively use it. 

Pack up your compilers and IDES, because it's camping time in Portland!

Portland Code Camp 3.0 is back May 19th and 20th!

Location: Washington State University - Vancouver, 14204 NE Salmon Creek Ave, Vancouver, WA 98686

Visit the site for more information.

Join members of the Visual Studio Team System product group to discuss features available in Visual Studio Team Foundation Server, Team Editions for Architects, Developers, Database Pros, and Testers. In addition, discuss what's new in the in the Visual Studio code name “Orcas” Beta 1 releases for Team Suite and Team Foundation Server.

Join the chat on Friday, April 27th, 2007 from 10:00am - 11:00am Pacific Time | Add to Calendar | Additional Time Zones

Yesterday, Microsoft's Developer Division (DevDiv) released beta 1 of Visual Studio "Orcas", which corresponds with the Connected Systems Division’s beta 1 release of the .NET Framework 3.5. Soma blogged this yesterday morning. Visual Studio "Orcas" enables developers and development teams to rapidly create Software + Services on the latest platforms, including the Web, Windows Vista, the 2007 Office System, and Windows Server "Longhorn".

As usualy, one of the most common questions about Orcas is, "When will it ship?". Well, here's Microsoft's official/public timeline:

Orcas Beta 1 will ship "Before TechEd Orlando in early June." - done! (see below)

Orcas Beta 2 will ship "In the North American summer."

Orcas RTM will ship "Before the end of the year."

BTW you can download the ready-to-go VPC images here (Team Suite) and here (TFS) of Orcas.

If you'd like to file bugs in TFS using a web page, perhaps for users that don't have VS2005 or the Team Explorer installed, there's a pretty clean example located here.

Now, I hear everyone crying out about Microsoft's purchase of TeamPlain and the web access available though that.  (The version one of the TeamPlain addin is now freely available for download here.)  I'm the first to admit that the TeamPlain solution is likely the best, however, there are times when you need to create your own solution.  And the primary reason for that is 'multiplexing', or supporting a large number of users who do not have TFS Client Access Licenses (CALs), by dropping everything into a single database, then having a triage individual, who does have a call, make the final decision to upload to the TFS server.  (More on that in a future post...)

Hallelujah!  You can now use WSS 3.0 with TFS 1.0 SP1!  This is great news!!!  For those of you who haven't seen WSS 3.0 as compared to WSS 2.0, you're in for a wonderful treat!  WSS 2.0 was missing that one critical tool that greatly assists the agile software development process - the wiki.  And WSS 3.0 plugs that hole!

Brian Keller, of Microsoft, has the BETA guidance for WSS 3.0 with TFS SP1 for the port on his blog.  Don't miss it!  As for right now, I'd recommending holding off on production server deployment until a few rounds of first adopters work out any possible kinks.  But if you want to be on that first round...   

Just to catch you up, Microsoft's Team Foundation Server v1.0 (released March 2006) only works with WSS 2.0. WSS 2.0 is the old version. WSS 3.0 is the new version, and launched with Microsoft Office 2007. It's full of great new features, but alas TFS won't integrate with it naturally. Even installing TFS SP1 won't get you there.

Thanks to Brian Keller, a Technical Evangelist for Team System, who has published a document on how to integrate TFS with WSS 3.0. As Brian explains, keep in mind that this is a "release candidate" of guidance that will eventually be posted to MSDN.

Now I've heard of a lot of things, but an RC of a guidance document?

One of the best things software development shops can do to improve productivity is to set Outlook to only check email once every hour (or 30 minutes at least).  This is because people tend to take quite a bit of time to get back to difficult tasks.  Email, and IMs, are difficult to ignore when that little "pellet dispenser" pops up on the lower left hand side of your screen.  And once your mind strays it's hard to get back on task.

A recent research project reported in the New York Times (link - free registration required), bears this out.  Here's the money quote:

In a recent study, a group of Microsoft workers took, on average, 15 minutes to return to serious mental tasks, like writing reports or computer code, after responding to incoming e-mail or instant messages. They strayed off to reply to other messages or browse news, sports or entertainment Web sites.

“I was surprised by how easily people were distracted and how long it took them to get back to the task,” said Eric Horvitz, a Microsoft research scientist and co-author, with Shamsi Iqbal of the University of Illinois, of a paper on the study that will be presented next month.

“If it’s this bad at Microsoft,” Mr. Horvitz added, “it has to be bad at other companies, too.”

So, turn off that email while you're coding!  (And driving!)

Last year, at PDC, I sat down with Adam Cogan, of SSW, during an MSDN magazine party.  Feeling the guilty pleasure of totally geeking out while a decent party was going on, Adam led a group of geeks through some of his very cool software tools.  Somewhere during the discussion, he mentioned that he deploys his unit test, along with a test runner, with his shrinkwrapped application.  That got my attention, since I'd never thought of them like that.  I called him on it, and he explained.  Now, there seems to be a visceral reaction from folks against the idea.  Here's WHY it makes sense to deploy unit tests and a test runner with you application:

1. Customer - "Your stupid app lost all my contact data!"
2. Help Desk - "Maybe I can help.  Go to Help -> Analyze"
3. Customer - "OK.  I see this list of green and red dots with text."
4. Help Desk - "Can you read me the line next to the first red dot?"
5. Customer - "It says 'Can't find database at C:\myapp\contacts.mdb'"
6. Help Desk - "Hmm...  Can you browse to that directory?"
7. Customer - "No, I deleted it to have room for more mp3's"
8. Help Desk - "Oh...  That's a file required for our app to run.  Did you subscribe to our backup service?"
9. Customer - "Yes."
10. Help Desk "Good, go to Tools -> Options -> Restore Contact..."

You get the idea.  It rocks for troubleshooting those pesky support calls from customers.  For a lot more information, and a very nice screenshot, see Adam Cogan's original posting on this topic!  You can find the specific recommendation in his menu unit tests best practice. (While you're there, check out the rest of his best practices, he has a huge number of great ideas.)

Unfortunately, you cannot ship your Team System unit tests with your application.  I know there's an NUnit to VSTS Unit Test converter.  Does anyone know if VSTS Unit Tests can be converted to NUnit or MbUnit unit tests, so that all of us using VSTS Unit Tests can implement this best practice?

UPDATE:  Adam Cogan claims he got the idea from James Newkirk (of NUnit fame).  That may be the case, but I'll have to credit Adam.  He's got so many best practices on his site (see this rule that covers shipping unit tests for an example) that if he didn't get the idea from Newkirk, he likely would have thought of it himself!

UPDATE TWO:  This IS Adam's idea!  James simply wanted a distributable test harness for developers to use!  I misunderstood his first comment to me!  (By the way, if you have comments on this post, or any other, please send email to steve+comments[at]accentient.com.  We've had to disable comments until we find a way to more effectively eliminate comment spam.)