Robert McLaws: Windows Edition

Blogging about Windows since before Vista became a bad word

June 2007 - Posts

  • TechEd 2007 Keynote Video: Doc Brown

    Back to the Future was one of my favorite movies when I was a kid. Most tech geeks grew up with Star Wars toys... I had a Back to the Future skateboard. I watched the first movie so many times I can practically recite it from memory.

    Microsoft often spoofs movies for their keynote videos, and this year was no exception. But while the "Napoleon Dynamite" Bill Gates video was probably the coolest one (come on, Jon Heder slapped Bill right across the face), this one was about as geeky as they come. And when Chris Lloyd came on stage, I got the feeling that he was thinking "So this is what Shatner feels like at a Star Trek convention." He definitely needed a cup of coffee and some cue cards. I was a little disappointed that they tried to make it too topical, instead of just spoofing the movie... plus they probably spent a couple hundred grand on licensing and production, and the "MSVSBS" detector was a $2 plastic horn... but oh well.

    Here's the video, thanks to the guys over at Neowin:

    [YouTube:pi3xmc1mpXQ]

    PostTypeIcon
    5,952 Views
  • TechEd Spoilers: 'Katmai' Gets Named, Storming the 'Acropolis'

    Filed under:

    A Microsoft employee accidentally let the cat out of the bag a bit early. In a post that has since been taken down, "esendal" has announced that SQL Server "Katmai" has been re-christened SQL Server 2008. The announcement was more than likely supposed to come at the TechEd 2007 keynote later this morning. It will be available for download at http://connect.microsoft.com/sqlserver, potentially as early as today.

    [via ActiveWin]

    Also more than likely due to be announced is Microsoft Code Name 'Acropolis', which is yet another Microsoft runtime (YAMR)™. This one leverages WPF to help build loosely-coupled applications. From the help file:

    "Acropolis" uses a composite application framework to address complex, changing business requirements. Composite applications integrate functionality as components that you can easily reconfigure or replace.

    For example, a composite application might display data from a remote database, but let you choose between a WPF and a Windows Forms user interface. It might also enable users to choose from multiple components to interact with the data.

    Composite applications often have a portal or "dashboard" look, but this is only one scenario of many. The important point about composite applications is that units of functionality remain loosely coupled to make change easier. Whether the change is a new business requirement or a user reconfiguration, making change easier makes improvement easier.

    Sounds like a pretty nice framework. When you leverage this functionality with Windows Workflow Foundation, you're got yourself a pretty adaptable application. Now if only I had the time to learn it...

    [via ActiveWin]

    I'm assuming that more information will be available on both of these later today. I'll post links when they're available.

    PostTypeIcon
    16,111 Views
  • Selling My Powerline Ethernet Adapters

    Well, since I got my new Wireless-N router, I won't be needing my Netgear HD Powerline Ethernet Adapters anymore. So I've put them up for sale on Craigslist. They were only used for a couple days, and didn't work well because of the wiring in my apartment complex. But I tried them at my girlfriend's parents house, and they worked just fine there. If anyone is interested in them, just drop me a line!

    PostTypeIcon
    17,762 Views
  • Followup to my Visual Studio EULA Post

    I want to make it clear (which it might not have been in my last post) that I don't condone Jamie's actions at all in this matter. The whole lack-of-addins thing was a well-known limitation, even if it wasn't clearly defined anywhere, and I don't think Jamie should have re-added the functionality after he took it out the first time. Plus I've heard rumors of other actions he took that, if true, I don't agree with.

    But Microsoft opened itself up to the problem in the first place with a EULA that could be interpreted to put practically every ISV in jeopardy, and could have solved it by simply publishing a document on MSDN called "Limitations of Visual Studio Express". That would have clearly defined what were "intentional limitations that could not be worked around", and everyone would agree that Jamie was in clear violation of the EULA. Then it wouldn't have been the "lose-lose situation" that Microsoft already knew it was getting itself into.

    At the same time, the lawyers should have taken all the emotion out of the argument, and stuck with the facts. How could he betray "thousands of VSIPs" when he's not a VSIP himself?  And I still challenge Microsoft to prove they lost any money on this (besides the time spent arguing, and the cost of the lawyers, of course). The lawyers should have stuck to the facts instead of writing what appeared to be the kind of note that a future ex-wife would write to her cheating husband.

    Based on Dan's comment in my last post, it looks like Microsoft will indeed clean up the EULA in their next revision of VS Express. And every other product division at Microsoft should do the same (Windows team, you guys still have some work to do). Vagueness does not engender the rich third-party ecosystem that is the basis for Microsoft's success, and should be eliminated for simple, straightforward language in the same vein as the changes already made to the Vista EULA.

    PostTypeIcon
    11,593 Views
  • Google Bought FeedBurner, Now What?

    So the rumors were true. FeedBurner has been assimilated by the New Collective. Well isn't that just fantastic, another service I left Google for has been bought by Google.

    I haven't decided if I'm gonna stay with them or not, but I did find out one great piece of information today: you'll be able to e-mail FeedBurner, and they'll delete your account, your feeds, and all your statistics before they are transferred over to Google. I don't know if they'll redirect your feeds somewhere else, or if you'll just be screwed like that, but I'll find out. But I only have 15 days to decide before my data becomes property of someone I trust less than FeedBurner.

    So here's the question, dear readers: Should I stay with FeedBurner, or should I move to a different service? Is there even another service out there that is anywhere in FeedBurner's realm? If not, should one be started? You guys use the feed way more than I do anyway, so let me know what you think I should do. Your feedback will be the primary factor in my decision-making process.

    PostTypeIcon
    3,269 Views
  • Weighing In on the Visual Studio Express EULA Debacle

    There is a cold chill in the air today. For those of you that don't pay attention in the developer world, there is a war brewing between Microsoft and a one-person ISV. At the center of the dispute is a ridiculously ambiguous portion of the Visual Studio Express EULA, which also happens to be at the center of the Microsoft/ISV relationship.

    Here's a little backstory: TestDriven.NET is an add-in for Visual Studio that enables code testing with a particular set of open source tools. It hooks into Visual Studio to provide the glue by which the various open source components can work together. It's a pretty great tool, especially if you can't afford Microsoft's expensive Visual Studio package that includes unit testing (which is a more expensive SKU then their lowest paid version).

    So what is the EULA section in question? Straight from Microsoft, below is the section in question (emphasis mine):

    9. SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways. For more information, see www.microsoft.com/licensing/userights. You may not
      • work around any technical limitations in the software;
      • reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;
      • make more copies of the software than specified in this agreement or allowed by applicable law, despite this limitation;
      • publish the software for others to copy;
      • rent, lease or lend the software; or
      • use the software for commercial software hosting services.

    This is a well-documented generality that a lot of people have a problem with, myself included. In the past, this clause has been used to prosecute software "crackers" who build tools to, for example, turn Windows XP Home into Windows XP Pro, or circumvent the software activation to steal a copy of Windows. This is the first time I've heard of this being used against a legitimate ISV. The repercussions for this are not to be underestimated. But I'll explain more about that in a minute.

    Dan Fernandez, the PM for Visual Studio Express, has explained his position in a couple of posts. What I find kind of funny is that the letter sent from Microsoft's lawyers in the UK is pretty over-emotional for a legal notice. For example:

    "Our client should not have to explain to you, a software developer, the significant commercial harm being caused by your unlawful activity. All software houses (to a greater or lesser degree) make available versions of their software which have limitations on their use, some often made available for free. It is for the software house to determine which of its software it wishes to make available to users and on what terms. A limited version of a piece of software may be given away as a marketing tool, or sold at a lower price to reflect its limited functionality; more sophisticated versions of the same software representing very valuable intellectual property may only be supplied at a higher price. Your activity subverts this model, depriving our client of very significant revenues. It is a model you will well appreciate as you employ it with your own products when you specify different licensing terms for three versions of your product, one for "Personal", one for "Professional", and one for "Enterprise". Your activity also causes wider damage in the marketplace by, amongst other things, creating dissatisfaction amongst Microsoft's many partners." (Emphasis mine)

    And I thought I was long-winded. So in between a really ridiculous primer on how software is sold, we have this sob story on how much money Microsoft is losing because of their product. For starters, there is a measure of intent that has to be taken into account. People who crack Vista do so to steal the software. Jamie's software doesn't serve the same purpose. People aren't downloading his product so that they can enable add-ins in Visual Studio, they're downloading his software to be able to write code that lets you test code you've written. Furthermore, I challenge Microsoft to be able to prove that it has lost any money whatsoever in the matter.

    In my opinion, the only one causing dissatisfaction among Microsoft's many partners is Microsoft, because their actions based on this clause throws the whole basis for Microsoft's ISV relationships into doubt. Microsoft is a huge company, and their software can't do *everything* people need it to do. Every day, ISVs build new software that build on or enhance Microsoft products by finding the functionality that Microsoft couldn't add in (for whatever reason), and fill in the gap.

    Visual Studio Express doesn't specifically say anywhere "Don't use add-ins", the functionality is just not there. So how was anyone supposed to know that was intentional? Microsoft misses blatantly obvious functionality all the time. I used to be an ISV, but I got out of the business, because you have to charge too much for components to be taken seriously by big development shops. If I were still in that business, I'd have to start factoring the risk of being sued by Microsoft into my business plan every time I build a new component that fills in one of Microsoft's many gaps. And that might keep me from building that component.

    All in all, this situation was handled badly by all parties involved. But the threat to sue was a *REALLY* dumb move on Microsoft's part, because it doesn't matter who was right, when Microsoft sues, they're wrong in the court of public opinion. Microsoft's team of 800 lawyers are supposedly pretty smart. Guys, it's time to put your heads together and clarify this part of the EULA for your products. And if there is specific techniques used to differentiate between your products, they should be clearly and succinctly defined. Then you would avoid ridiculous misunderstandings of unnecessarily obtuse agreements (is this a license agreement or a patent?) and, oh by the way, you wouldn't piss off the people who drive most of your sales in the first place.

    In conclusion, both parties should retreat to their corners. Jamie should take that functionality out of the product, and Microsoft should clarify it's license. If the amended license sufficiently states the limitations of the product that should not be circumvented, then Jamie will have no choice but to keep that functionality. But Microsoft, if you can't give your supposed partners that courtesy, then why should they return the favor?

    And here's the drill, Microsoft: if you're just doing this because you plan on putting unit testing in the core product with "Orcas", the sh!t will probably hit the fan. I highly doubt that your customers will take that lying down.

    PostTypeIcon
    22,593 Views