• Brad Wilson blogs about SvnBridge, a tool that lets you use Subversion clients like TortoiseSVN to talk to Team Foundation Server. While I think that’s cool, I wonder is anyone interested in subversion clients other than TortoiseSVN? For example, will people choose AnkhSVN instead of the Team Explorer Client?
• Speaking of TortoiseSVN, I wonder if those guys are interested in building a TortoiseTFS project? I did find two other TFS shell extensions projects: Dubbelbock TFS and Turtle, though neither appears as full featured as Tortoise.
• Scott Guthrie details VS08′s multi-targeting support. Of course, the three versions of the .NET Framework VS08 can target all use the same underlying runtime, which probably made it easier to build.
• Michael Platt refactors Don Box’s original tenets of service orientation so he can include some information about how these services get built.
• Scott Hanselman tackles the tricky question of assembly granularity.
• PowerShell Analyzer is now available for purchase. Among other things your $59 gets you, besides a 50% savings, is “Feature request priority“. That’s pretty cool. I wonder how many other micro-ISV’s take the approach of “pay me now and you get to help me pick some of the new features.”
• Brandon LeBlanc
  
  writes about dual monitor support in Vista. I’m loving the dual monitor support, though I have a somewhat strange setup. I keep my primary monitor rotated in portrait mode, which is great for reading and writing. I typically use my second monitor for blogs and mail. I even wrote a custom multi-mon wallpaper utility so I could easily generate new wallpapers for my non-standard monitor layout, including bitmap rotate support. If there’s interest, I can post it. (via Sam Gentile)
• Nick Malik continues to write about Mort, with the usual response from the usual folks. I liked his point that “You cannot fight economics with education”, but otherwise I’m staying out of this discussion.
• In the same vein, Martin Fowler writes about Technical Debt. I completely agree with his hypothesis that short changing design may save time in the short term but will cost much more in the long term. However, the problem is that the people who are making the tradeoff – i.e. the people paying for the project NOT the people building the project – either don’t understand the tradeoff or are more than happy to sacrifice the long term cost for the short term gain. How are most projects measured? Being on time and on budget with the planned set of features. Very few projects – and none that I’ve ever seen – are goaled on long term maintainability. Until you can change that, this issue will continue to linger.

• My wife loves me. I’m a very lucky man.
• I’m starting to really dig Safari Books Online. Having a tablet really helps here, I can sit in bed and read and it’s ALMOST like reading a real book. Is there an offline experience? Something like the NYTimes WPF Reader app would be killer.
• I’m not a Twitter guy, but I like the idea of using it to publish CI results. Not quite as cool as using the Ambient Orb, but close. (via DotNetKicks)
• Soma details the dogfood usage of TFS in Developer Division. Sorta interesting if you’re into knowing that stuff. Brian Harry apparently has much more.
• I realize that linking to Pat Helland every time he writes something is fairly redundant. If you want his feed, you know where to find it. But he writes great stuff! The latest is Accountants Don’t Use Erasers, which talks about append-only computing. His point that the database is a cache of the transaction log is mind blowing, yet makes total sense.
• Bruce Payette blogs a PS DSL for creating XML documents.
• Jesus Rodriguez details WCF’s new Durable Service support in .NET 3.5. I get the need for the [DurableServiceBehavior] attribute, but do I really have to adorn each of the service methods with [DurableOperationBehavior] too? That seems redundant. Also, I wonder how this looks at the channel layer?
• Speaking of WCF’s channel layer, I recently picked up a copy of Inside Windows Communication Foundation by Justin Smith. This is the first book I’ve found that has more coverage of the channel layer than the service layer, so I like it.
• Dare writes about Web3S, Windows Live’s general purpose REST protocol. Apparently, WL started with Atom Publishing Protocol, but found that it didn’t meet their needs around hierarchy and granular updates. David Ing says it’s “not that similar” to my concept of REST, but I going to read the spec before I comment.
• Scott Hanselman writes about how he learned to program and some thoughts about teaching his son. Patrick has recently started expressing interest in programming (he want’s to do what Daddy does). At four, I’m thinking I’ll start him on Scratch (though ToonTalk looks interesting). As he gets older, I was thinking about Squeak, though I’m a smalltalk noob. I really like Scott’s idea of creating a connection to the physical world via something like Mindstorms. Patrick loves Lego almost as much as his dad, so that would be cool.

Last week, I asked a REST Question: is it still REST if you don’t use HTTP? My interest in durable messaging is well documented, so I want is to see a RESTful approach combined with a durable messaging. We all know my durable messaging tool of choice, though I’d trade SSB in a second for something that provided durable duplex messaging in a standard way.

Anyway, there were some fairly interesting responses that I wanted to highlight.

Probably most interesting to the discussion at hand was John Heintz‘ comment pointing out the existence of “Waka” ,  a new transfer protocol to replace HTTP from Roy Fielding. The fact that Dr. REST is working on a new protocol that’s designed to be more RESTful than HTTP should put to bed any REST “is and only is” HTTP arguments.

Erik Johnson agrees that you can separate REST and HTTP, but he thinks I ought to call it something else. He suggests “resource-oriented” – have we created a new TLA here? Are you down with ROA, ROAD, ROD, ROP and all the other acronyms we could spawn?

Nick Malik breaks out the IFaP acronym – Identifier, Format, Protocol – and points out “Each of the successful Internet standards, from HTTP to SMTP, has an IFaP at the heart of it.” But does anyone think SMTP is RESTful? I don’t. I think standardization of IFaP’s is on par in importance with RESTfulness, but they’re orthogonal. That is to say I think Nick’s wrong – I’m guessing we’ll go a few rounds on this when he gets back from Nashville – or should I say, if he gets back? 😄

Arnon Rotem-Gal-Oz has been wondering about REST without HTTP the same way I have, but he doesn’t really go into detail as to why. I want durable messaging, Arnon mentions something about topic hierarchies. Couldn’t you do that with HTTP, Arnon? He also points out a new DDJ article on REST. It’s good, if high-level overview-y.

Pat Helland writes that Every Noun Can be Verbed. It’s more related to CRUD is CRAP than REST == HTTP, but it’s well worth the read. His point about using filling out a form being CRUD, but then handing the form over to someone else being an invocation of behavior is fairly eye-opening. As long as you “interpret the durn’ things with the correct semantics”, it doesn’t really matter if they’re nouns or verbs.

Last but not least, Ted Neward and Adrian Trenaman discuss SOAP vs. POX over on The Server Side. They focus too much on SOAP encoding (isn’t that dead yet?), but near the end Ted points out: “Problem is, REST assumes that you want to carry all of the state in the payload itself, and for a modern enterprise system, or, hell, even for a game, that’s not always a safe assumption.” Doesn’t address my questions about using REST without HTTP, but a very good point nonetheless.

• Akira in HD from XBL Video Marketplace?
  
  Coolness.
• Omar Shahine has the WL Hotmail + Outlook scoop. Download it here. I’ve used this product off and on over the past few years. Typically, I would use it, love it, but then never get around to reinstalling it after a repave since it was subscription-only product.
• Microsoft releases eScrum project management tool. I’ve seen this internally but haven’t used it yet. However, I have no doubt that the cool kids will deem it “not hot” in favor of Mingle. (via Larkware)
• Ted Neward writes at length about relational databases, object databases and OR mapping. Ted may be Switzerland when it comes to platform, but he has no problem taking sides and mixing it up when it comes to data & object persistence. He makes some interesting points that mostly boil down to “different tools for different jobs”. Also, has the dual schema problem entered the general vernacular, or just Ted’s?
• Nick Malik survives his trip to Nashville and has some thoughts on Ruby, Microsoft and alpha geeks. His point about the alpha geek track record (he sites Powerbuilder, Delphi and EJB) is spot on. This is something I’ve been thinking about since ETech last year. How good are alpha geeks at trendspotting? For every technology they adopt that makes the mainstream, how many don’t? I’m guessing quite a few more than the three Nick mentions.
• Speaking of alpha geeks, this whole ALT.NET silliness reminds me of the famous Groucho Marx quote: “I don’t want to belong to any club that will accept me as a member.” Though maybe I’m just bitter because “Working at MS” has been deemed “not hot”. 😄

I’ve got over 500 unread news posts and 200 emails in my inbox to process. So this is nowhere near comprehensive.

• Clarius released the June 07 CTP of their Software Factory Toolkit. Big new feature in this drop is T4 Text Template editor that has syntax highlighting and eventually intellisense. They also released the May 07 CTP of VSSDK Assist, previously known as VSIP Factory. Haven’t played with either yet, but it seems like a good time to be a tool builder.
• PowerShell hits a million downloads in six months. No surprise there, IT’S FRAKING AWESOME. Jeff Snover details seven MSFT products using PS, promising many more that he can’t talk about. See earlier comment about being fraking awesome.
• Speaking of PS, I don’t “get” Server Core because it doesn’t support managed code. So no PS for Server Core. They announced @ TechEd that Server Core will support IIS 7, but since there’s no CLR you can’t run ASP.NET. As far as I’m concerned, no PS and no ASP.NET is below the minimum threshold of usefulness. I realize it’s technical limitation related to the current factoring of the .NET Framework and I assume some team somewhere in Redmond is working on fixing it. But what’s the point of releasing Server Core in the meantime?
• QUT releases version 0.8 of their Ruby.NET compiler. Given that the IronRuby guys bootstrapped by licensing the Ruby.NET compiler, I wonder how these two projects will evolve side by side.
• Speaking of Ruby, JRuby has gone 1.0. Congrats!
• At TechEd, I saw my friend Steve Jones from Capgemini, and it’s not this Steve Jones. Woops. But CRUD is still CRAP.
• Pat Helland breaks Scott Hanselman’s Rule #2 and details how he “lost a Megan“.
• My ex-teammate David Hill has been busy with Acropolis. If you are even the slightest bit interested in this technology, you should be reading his blog.
• Microsoft acquired a company called Stratature last week. I don’t typically track MSFT acquisition news + it was lost in the noise of TechEd. But Roger Wolter thinks it’s a great move and that Stratature’s Master Data Management hub product is one of the best. Given the importance of MDM in SOA, I think I need to go learn more about this product.