I read that Google runs buses. Headline material in the New York Times. Impressive. Ehh. Here at Microsoft, buses are run by the King County Metro Transit system and we all get a free Flexpass. And our shuttle system is constrained to connections within and between the campus locations in and around Redmond. Of course that's just cost effective, logical and boring and therefore not newsworthy, I guess.  

COM Is Love.

Disagree? Stop reading.

Agree? Still feel it? Well, I just learned that there's a very unique way you can show your love for COM. Own it!

Own it? Yes, I'm completely not kidding. We've got an open position for a Program Manager to own COM+, DCOM, RPC, the WCF/COM Integration, System.EnterpriseServices and all the future goodness that we're going to stick into Longhorn Server and future versions of Windows to keep COM going and make it increasingly integrated with all the goodness that we're working on for the future of distributed systems in the years to come. COM dead? Pfft. 

If you are interested and have difficulties figuring out how to work the job web page (that is the preferred way, however) send me a mail with your resume to clemensv at microsoft.com. And mind that my email address just serves as a proxy here so be as serious as you would be about applying for a job with someone whose blog you don't read... 

Wow! I'm watching the Oscars with my wife and she just thought I completely lost it during the last commercial break. I actually started cheering. Why? I've seen the first Microsoft commercial that made me think ... Wow. The firm starts getting how to do this. Short, witty, provocative, impactful. Cool.  "Wow" Cleveland, 1946. "Wow" 2007. More of that please.

I'm busy at a conference but just stumbled upon Yahoo Pipes via TechMeme and Dare. The little bits I read about it make that quite interesting to me (and put a big grin on my face) specifically because of this piece I wrote in 2003 and which also got some attention back then. I claim prior art

WS-* or REST? Is there an epic battle? How does Microsoft think about a big chunk of the web development community ignoring the beloved WS-* specs and preferring "HTTP programming"? Answer: We think that people make these choices of good reasons and we like and support any way you want to write services. As a matter of fact, we're engaging with the community to make both, the WS-* stack and the HTTP/REST better to work with and make them a safer environment for, well, everyone.

In the spirit of the last statement, Bill Gates has just announced at the RSA conference (and our Chief Identity Architect Kim Cameron blogged) that we're working with JanRain, Sxip, and VeriSign to integrate CardSpace with OpenID and help making OpenID more resistant against phishing attacks by allowing relying parties to request and be informed of the use of phishing resistant credentials. We'll also integrate OpenID into future Identity products. On the OpenID side, you can expect direct support for CardSpace Information Cards on infrastructures that use the OpenID products from these vendors.

If you ask me, that's pretty big. But working here it's not as much of a surprise as it might be for people on the outside. We're very closely looking at what the community is building and asking for and if we see technologies or initiatives out there that gain lots of traction (such as REST programming, JSON or OpenID) I don't see a "wasn't invented here" attitude around anymore around here these days. We'll have REST support and JSON support (and RSS and Atom) in the next version of the .NET Framework and we'll have broad support for OpenID in our Identity infrastructure. At the same time we'll continue to work with industry partners to make the enterprise-messaging features in WS-* work better and, as demonstrated by the OpenID announcement, that "WS-* stuff" actually comes to the rescue of OpenID for phishing defense.

Doug Purdy, the (my) Group Program Manager of the Connected Framework team (owning WCF and WF) just got email:

Dear Douglas, 

Last year you emailed us regarding .NET Framework 3.0. We are emailing you to let you know that we have installed .NET Framework 3.0 on our webservers.

 

We continue to improve our product so please keep an eye out on our service.

 

Have a great day.

 

DiscountASP.NET

- Microsoft Gold Partner

- 2006 and 2005 Product of the Year: asp.netPRO Magazine Readers' Choice

- Best ASP.NET Web Hosting: 2006 and 2005 asp.netPRO Magazine Readers' Choice

- Best .NET Hosting Provider: .NET Developer's Journal 2005 Readers' Choice

How is your ISP doing?

I've spent the last 1 1/2 weeks doing one of the most fun (seriously) work assignments that each Program Manager of our team gets to do every once in a while: Servicing. So until yesterday night (I'm flying home to Germany today) I was in charge of ASP.NET Web Services and Remoting. An even though these technologies have been out there for quite a while now, there are still situations where stuff breaks and people are scratching their heads wondering what's going on. Overall, it was a very, very quiet time on the bug front though.

The one issue that we found on my watch is that you can configure ASP.NET Web Forms in a way that it breaks ASP.NET Web Services (ASMX). We are shipping one ASP.NET Web Page (.aspx) with ASMX and that unfortunate interaction manages to break that exact page with an error that's hard to figure out unless you have substantial ASP.NET knowledge and you have enough confidence in that knowledge to not trust us

If you globally override the autoEventWireup setting in the <page/> config element in the ASP.NET web.config and set that to "false", the DefaultWsdlHelpGenator.aspx page (which sits in the CONFIG directory of the Framework) becomes very unhappy and fails with a NullReferenceException, stating "Object reference not set to an instance of an object." and showing you some code that's definitely not yours.

What happened? Well, the file is missing a directive that overrides the override of the default. The fix is to go edit the DefaultWsdlHelpGenerator.aspx file and add the line:

<%@ Page AutoEventWireup="true" %>

That will fix the problem.

Now, the big question is: "Will you put that into a service pack?". While there's obviously a bug here, the answer is, in this particular case, "don't know yet". Replacing or editing that particular file is a potentially very impactful surgery done on the patched system given that the file is there in source code and in the config directory because you are supposed to be able to change it. Could we touch changed files? Probably not. Could we touch unchanged files? Probably? So how would you surface the difference and make sure that the systems we couldn't patch would not suffer from the particular bug? What's the test impact for the code and for the service pack or patch installer? How many people are actually using that ASP.NET config directive AND are hosting ASMX services in the same application and/or scope? Is it actually worth doing that? Making changes in code that has already shipped and is part of the Framework is serious business, since you are potentially altering the behavior of millions of machines all at once. So that part is definitely not done in an "agile" way, but takes quite a bit of consideration, while it takes just 10 seconds and notepad.exe for you.

It's been slashdotted and also otherwise widely discussed that Google has deprecated their SOAP API. A deadly blow for SOAP as people are speculating? Guess not.

What I find striking are the differences in the licenses between the AJAX API and the SOAP API. That's where the beef is. While the results obtained through the SOAP API can be used (for non-commercial purposes) practically in any way except that "you may not use the search results provided by the Google SOAP Search API service with an existing product or service that competes with products or services offered by Google.", the AJAX API is constrained to use with web sites with the terms of use stating that "The API is limited to allowing You to host and display Google Search Results on your site, and does not provide You with the ability to access other underlying Google Services or data."

The AJAX API is a Web service that works for Google because its terms of use are very prescriptive for how to build a service that ensures Google's advertising machine gets exposure and clicks. That's certainly a reasonable business decision, but has nothing to do with SOAP vs. REST or anything else technical. There's just no money in application-to-application messaging for Google (unless they'd actually set up an infrastructure to charge for software as a service and provide support and proper SLAs for it that is saying more than "we don't make any guarantees whatsoever") while there's a lot of money for them in being able to get lots and lots of people to give them a free spot on their own site onto which they can place their advertising. That's what their business is about, not software.

Apparently there's a little blog tag game spreading that Gerald from Sun Microsystems desperately wants to pull me into. Ok. I'm game.

My 5 things:

1. The most CDs I have from a single artist or band are by Prince (& the Revolution, & the New Power Generation). I skipped most of the trash he put out while he was trying to get out of his Warner contract, but unfortunately not the horrid album Come for which I still want my money back. My favorite album is Sign of the Times, followed by 1999. The new 3121 isn't too shabby either.

2. The first game I ever programmed all by myself on my ZX81 (in 1KB!) and not by just typing in a listing from one of the difficult-to-acquire computer magazines (that's how things were back in the day) I wrote in 1984. It was a PacMan knockoff. I lost all work at least five times because the Sinclair's way of saving programs to the cassette tape was not very reliable, to put it nicely. Space Invaders was next.

3. The F. in Clemens F. Vasters stands for Friedrich. My grandmother (father's side) insisted me having that name in honor of my grandfather who fell in France in 1944. By what is known, he was a motor courier and got shot by the French Resistance. He's buried at the German War Cemetary outside of Andilly (near Nancy), France.

4. I currently have 180,000 hard-earned bonus miles with KLM/Air France and 110,000 with Lufthansa. I am qualified as Lufthansa Senator (Star Alliance Gold) through 2/2010, since Lufthansa stacks the 2 year award periods on top of each other when you qualify again in the first year of your award period. I am losing my Gold status with KLM/Air France this next April. No more lounge access in Schiphol and no more skipping the Economy check-in line. That sucks. In my job here at Microsoft I will unlikely requalify for either, because I'm not doing much of the crazy traveling anymore. I've been to 48 countries in the past 4 years.

5. I turned down an invitation to interview for a job with the Microsoft COM/OLE team in 1995. They had first approached me in 1994 and the PUM who was driving that at the time dropped the ball after the first contact. He came back with an apology for not being as thorough about the process as he should have been - some 8 months later. When that happened I was locked in a 2 year contract heading the NY office of the German company I worked for, so it ended up taking 11 years until I actually landed just at the division that can trace quite a few of its roots back to that team. I got the COM/OLE team's attention by fighting (and winning, if there is ever such a thing) a huge email flame-war on the Microsoft OLE CompuServe forum where the product manager of OpenDoc at Novell (who had just acquired WordPerfect at the time and got into OpenDoc that way) tried to convince everyone that he had the superior technology in hands. I wish someone had a backup of these forums. I am sure the conversation is horribly embarrasing from today's perspective.

So here are my 5 things. And the tag goes to ...  Udi, Daniel, Don, Nicholas, and Mr. Maine.