Absolutely hilarious story of a banking computer system crash... I had heard it before from someone before but didn't know if it was true or not.  Take a look:  http://www.thehumorarchives.com/joke/A_true_story_of_computer_stupidity

In March 1992 a man living in Newtown near Boston Massachusetts received a bill for his as yet unused credit card stating that he owed $0.00. He ignored it and threw it away. In April he received another and threw that one away too. The following month the credit card company sent him a very nasty note stating they were going to cancel his card if he didn*t send them $0.00 by return of post. He called them, talked to them, they said it was a computer error and told him they*d take care of it.

The following month he decided that it was about time that he tried out the troublesome credit card figuring that if there were purchases on his account it would put an end to his ridiculous predicament. However, in the first store that he produced his credit card in payment for his purchases he found that his card had been canceled. He called the credit card company who apologized for the computer error once again and said that they would take care of it. The next day he got a bill for $0.00 stating that payment was now overdue. Assuming that having spoken to the credit card company only the previous day the latest bill was yet another mistake he ignored it, trusting that the company would be as good as their word and sort the problem out. The next month he got a bill for $0.00 stating that he had 10 days to pay his account or the company would have to take steps to recover the debt.

Finally giving in he thought he would play the company at their own game and mailed them a check for $0.00. The computer duly processed his account and returned a statement to the effect that he now owed the credit card company nothing at all. A week later, the man*s bank called him asking him what he was doing writing a check for $0.00. After a lengthy explanation the bank replied that the $0.00 check had caused their check processing software to fail. The bank could not now process ANY checks from ANY of their customers that day because the check for $0.00 was causing the computer to crash. The following month the man received a letter from the credit card company claiming that his check had bounced and that he now owed them $0.00 and unless he sent a check by return of post they would be taking steps to recover the debt. The man, who had been considering buying his wife a computer for her birthday, bought her a typewriter instead.

Ed B.

Okay... so in hindsight this is so stupid but I only post so it won't cause you as much time as it did me!

So I'm in VS 2005 after installing the Orcas Beta 1 and I needed to get something from the Team Foundation Server... BUT I COULDN'T!  All of the context menus on the files in Source Control Explorer kept telling me that there were "No Commands Available."  "I don't think so!  We're not playing this game" said me to the computer. :)

Of course my first thought was that it might have had something to do with the Orcas install.  So I did a reinstall of both VS 2005 and Team Explorer but it didn't help any.  Aggravated now I begin my quest for the answer.

I don't know how it happened but the fix is simple:  Make sure Team Foundation Server is selected as the source control plug-in.  You can go to Tools --> Options (make sure you have the "Show all settings" option is checked at the bottom of the dialog) and select this plug-in.

GRRRRRR... Okay... back to productive work now.

Ed B.

Right now there are limited training resources for learning WPF and pretty much a non-existence of proven patterns and practices.  All of these assets will eventually come to the developer community as more people adopt the technology.  For right now, I would recommend this book for learning and as a keeper for a decent reference book.

Title: Windows Presentation Foundation Unleashed
Author(s):  Adam Nathan
ISBN-10: 0672328917
ISBN-13: 978-0672328917
Publisher: Sams

Some of the things that I really appreciated out of this book:

· This is truly a value-add, especially for a “visual” technology. There are other WPF books that don’t have a single screenshot and it is extremely helpful to have the visual side of WPF represented throughout the book.

· XAML Demystified and Important New Concepts Chapters -- I’m really happy that he did this at the beginning of the book and is where any beginner of WPF or Silverlight (formerly WPF/E) should start the learning process.

- Organized Extremely Well:  It's great if you want to read it from cover to cover or hit a particular topic.  I always give a book the "Index Test" and check to make sure I can easily find the most common WPF topics.

So, be sure to check it out!  Let me know what you think about it too.

Ed B.

Just a quick post to spread the word about supporting "Team Hanselman". Click the links below to help him support the "Fight Against Diabetes".

Ed K. and Ed B.

"TeamPlain is a web front end for VSTS that enables users to access the majority of TFS functionality from within a Web browser.  The focus of TeamPlain is on work item tracking but it also includes some valuable version control capabilities (like viewing history/change sets, diffing files, browsing the source base, etc.), some SharePoint integration, Reporting services integration, and some upcoming build support.  TeamPlain gives VSTS a new avenue to reach a broader array of people within the development team who don’t use Visual Studio today and don’t want to install Visual Studio clients on their machines.  It also improves reach by enabling some access from non-Windows clients.

TeamPlain has been in the market for about a year now and has been very successful.  Many of our VSTS customers use TeamPlain today and are very satisfied with it.  Our advisory council and other customers have been telling us for the past year that we need a web UI for VSTS and that TeamPlain would be a great solution for us.  We’ve listened, looked very closely at the product and concluded that they are right.  Today is the culmination of a long process and the beginning of another.

TeamPlain will become Microsoft Visual Studio Team System Web Access.  Effective today, TeamPlain is available, at no additional charge, to users who own a Team Foundation Server and can be downloaded from here.  It will be accessible by any user properly licensed with a TFS CAL.  Support will continue to be provided by the current staff via the DevBiz online forums.

Over the next few months, we will be rebranding TeamPlain as a Microsoft product and running it through our release process.  When that is complete, we will be releasing it as a VSTS Power Tool, transitioning support to the Microsoft forums and beginning CSS (phone) support.  In the Orcas timeframe, we will be releasing Team System Web Access as an official, documented, localized, and officially supported component of Team Foundation Server.

A look at the product

I've included a few screen shots here to give you a flavor for what TeamPlain looks like and what it can do:

Some likely questions

What version of TeamPlain are you releasing? - The initial download that is available today is TeamPlain V1.0.  After we have run it through the Microsoft release process, we will be releasing TeamPlain version 2.0 as a VSTS Power Tool.  V2 includes some cool new features, including Viewing/Managing builds, additional version control capability, AJAX support for a more responsive experience and larger project support, and much much more.  Ultimately we will be incorporating V2 (or a derivation of it) into the official product in the Orcas timeframe.

What is the Microsoft release process? - It is a long checklist of things (I think about 20 or so) that we have to do before we release any product.  It includes security reviews, scans for geo-politically incorrect terminology, test sign-off and much more.

When is "the Orcas timeframe"? - If I told you I'd have to kill you.

No, seriously, when is it? - Seriously, I can't tell you :)  What I can say is that we have been releasing CTPs for Orcas for a good while now.  We are currently working on getting ready for Beta 1.  Keep your eyes and ears open over the coming months for more news about it.  I'll have to let you draw your own conclusions about how long it will take after Beta 1 releases.  Our philosophy is to get the product to you early, in many forms, CTPs, Betas, RCs, etc and use your feedback on when you believe it is ready to help guide us.

Why do you say "the Orcas timeframe"? - Because, as I mentioned, Orcas has been in the works for a while now and we are just adding web access to the line-up.  It's going to take us some time to work out the details of how it fits into our schedule and I am expecting that it may not actually ship on the same day as the rest of Orcas but rather in the same timeframe.

How does this relate to CodePlex? - I think of them as different things, although clearly there is some overlap.  TeamPlain and CodePlex both have web UI for some overlapping areas.  Over time, we may look to see what we can share but we'll see how that evolves.

Does this mean I don't need TeamPrise any more? - No, not if you do X-Plat development and/or want Eclipse integration.  While TeamPlain can provide some cross platform access via the browser, it is not designed to provide the full set of capabilities that a developer would use: IDE and editor integration, command-line access for scripting, full version control access, etc.

Is Microsoft using TeamPlain internally? - Some groups are, yes, but it isn't broadly used yet.  The IT group probably uses it the most.  We installed a pre-release copy on the DevDiv dogfood server to experiment with it.  We are in the process of rolling it out to all of our internal users now.  I'll probably blog about the progress of this over the next couple of months.

What happens if I call Microsoft support about TeamPlain now? - We are working with our support organization to prepare them to support the product.  They are expecting to begin supporting it when we release it as a Power Tool in a few months.  I wouldn't be surprised if you run into some people in support who don't know anything about the product today.  I expect over the next couple of weeks we will educate the front line phone representatives on how to route calls for it.  Until we begin Microsoft based support in a few months, you will be directed to the DevBiz forums for answers to your questions.

In closing

This is a big step forward for Team System and I hope you are as happy about it as I am.  The future is looking brighter every day!

Brian "

Source: Microsoft Acquires TeamPlain!

Ed K.

I recently gave a talk at the Dallas BizTalk User Group on using WMI with BizTalk Server 2004/2006.

Sorry for the delay on posting the slides and links for download.

WMI Code Creator v1.0
Scriptomatic 2.0
WMI Diagnosis Utility -- Version 2.0
WMI CIM Studio

WMI.ppt (314 KB)

Ed K.

I ran across the issue of my "Code Snippets Manager" not being visible in my tools menu. I searched the web for an resolution to my problem but just found other people having the same problem with no answer. So I search around the IDE for a while till I found out how to get it added to the tools menu (wasted productivity).

 Here is a screen shot of the tools menu without the "Code Snippets Manager".

To resolve this issue go to the Customize option in the "Tools" menu. Go to the Commands tab and select "Tools" from the listbox. On the right side you will see "Code Snippets Manager", select it and drag it to your "Tool" menu and drop it in to place.

Now you are good to go.

If you hate having to search the IDE for options that you cannot find easily, then hopefully, I have saved you some time :)

Ed K.

The SDK consists of two different types of libraries, Implementation and the Interface. I love this API, they developed it for ease of use and scalability for future functionality in mind. The Implementation assemblies are not publicly expose and undocumented (protecting the developer from himself ;) ). The Interface assemblies are the interface to the implementation assemblies. There are several benefits to having the SDK architecture this way.

• Do not have to add references to implementation assemblies, freeing up the the possibility of being too tightly coupled to the implementation logic when the assembly version could change anytime.
• Follows the rule "Program to the Interface and not the implementation"

This API architecture style follows very much inline with how MS did the Team Foundation Server Object Model.

The SDK allows the develop to tap into any area of MOA2007:

• UI Add-In
• Business Logic Add-In
• Reporting Applications
• Integration Applications
• Specialize Applications

The SDK is packed full of samples and the documentation is right on.

I know, I know.... Accounting software is extremely boring but as my partner in crime Ed B has pointed out to me numerous time "This software is essential to business" and accounting software only has the minimal functionally in accordance with accounting needs but business never works great with "out of the box" functionality, sure it works but we want the software to match the process of the business. Being able to add value to accounting software with ease via a powerful API is exciting, the possibilities are endless and there is much money to be made with add-on's. This is a great API for ISV's and "Micro" ISV's.

The Interface assemblies in the SDK are versioned. I dig this. Let me break this down. Since we are programming to the interface and not the implementation, MS can change stuff up in the implementation assemblies and it will not break my production code. But what if they need to change some stuff up in both layers to add new functionality that they want to expose to the developers. In this case they would develop a new Interface assembly and note it as "IwhateverV2". As a SDK consumer I can use this new interface assembly or I can not, and my code will work just fine. To get a some of this new functionality exposed in the new Interface I can upcast my return Interface to the new object. Currently there are 2 versions of the interfaces in MOA2007, all the new Interfaces are appended with V2, which makes it very easy to keep track of what's what. For example: when MOA2007 was Small Business Accounting we had IAccountFactory now that it is Office Accounting we have IAccountFactoryV2. We can still use the old if we want. The rule of thumb is, If you are creating a new project with MOA2007 then use the V2 interfaces, If you already have production code and are writing new code or doing maintenance coding for the same project you will probably want to upcast to the new interface version.

Ed B and I will be developing some good examples using this SDK over the next few weeks to share with the community. We are very excited about MOA2007.

Ed K.

"The Team Foundation Administrator's Guide" is available for download here.

The Team Foundation Administrator's Guide is a comprehensive guide that covers procedures for administering Team Foundation Server, including planning, daily operations, recurring tasks, and infrequent operations. Use this administrator's guide to manage Team Foundation Server.

Note: The Team Foundation Administrator's Guide now includes content that was previously published separately in the Team Foundation Planning Guide, which is now deprecated.
(Microsoft 2007)

Ed K.

Take a look at this....

For some reason the clock in my system tray is not updating.  Any ideas?  I hovered over it a ton of times and no refresh... Very STRANGE!

Ed B.