• mwinkle.blog

    SOA&BP Conference Announcements, "Oslo"


    This morning at the SOA&BP Conference, we talked about Oslo for the first time.  For me, this is a big day, as it marks the point where the rest of the world knows what a lot of people have been and will continue to be working on.  Robert Wahbe, the VP of Connected Systems, mentioned in the keynote that Oslo can be best viewed as a series of investments that span a number of release cycles.

    What does this mean for me, a WF developer (note, these are my interpretations).

    • A vehicle for further investments in WF and WCF.  There will be a ton of enhancements in order to enable new scenarios, take the idea of modeling processes in an executable workflow to the next level, and drive performance and functional stuff.
    • Moving WF to the next level, by making it a first class citizen in this modeling world, by making rules and other artifacts get elevated into a way to modeled, managed, deployed and monitored.
    • Getting a chance to look at what people are doing with v1, and what lessons we can learn from it.  In Orcas, the stuff that we did was purely additive.  This longer release gives us a chance to enhance and improve and address things that we couldn't do in the Orcas timeframe.  There's some really exciting work going on here that I'm looking forward to talking about more in the future.
    • Finally, it gives us a better way to tell the WF hosting story, in that we will have a host and way to manage and deploy and execute WF and WCF in an host we will deliver, rather than requiring a "build on your own" approach (which still remains an option for folks who have specific hosting requirements).

    Our marketing folks always get nervous when we start talking about "revolutionary" technology (although, maybe it would get us some more Apple 1984 like commercials :-) ).  I've always seen workflow as a very transformational technology.  I see the things that are coming in Oslo as a very natural, evolutionary step, in the process of what I believe has been, and will continue to be a revolutionary way of making us be more productive developers.

    Finally, given some of the past history people have had with version numbers, I would not get caught up in the version numbers mentioned in press release.  As one of the marketing guys told me, "The quotes mean something," which, translated means "The numbers are just placeholders indicating a major release beyond where we are currently at."

  • mwinkle.blog

    Activities Survey


    So, we're getting close to .NET 3.5 getting out the door, and as always we're thinking about what comes next.  The activities team is looking how to make activities better going forward, and they are very interested in what you have to say, how you have been using them and how you'd like to use them.

    This feedback will help us understand how to shape the future of things and how we should think about the pain points you are experiencing.

    Fill survey out here!

  • mwinkle.blog

    .NET 3.5 on Channel9


    Following the big announcement last week, I got tapped to do a quick c9 interview with Shawn Burke.  Check it out here if you have 11 minutes or so to spare and want to see what the .NET source debugging will look like.

    Additionally, I see on the homepage that Jack is talking about the add-in framework in the latest video there.  Folks, if you work on a project where you want to allow add-in functionality, or have the need to version components separately and distinctly from the host, you need to check this out.  There are a few moving pieces and parts, but if you need to enable this scenario, investing up front in thinking through these bits and pieces will be enormously helpful.

  • mwinkle.blog

    Dogs and Cats Living Together, Mass Hysteria (or, Source Available for the .NET Framework)


    The title quote brought to you courtesy of the original Ghostbusters film.  As Scott just announced on his blog, we're making the source available under the Microsoft Reference License (MS-RL).

    This is cool.  But the really cool part of this is that there will be symbol server in the cloud that will let you dynamically, and auto-magically, download the symbols and source on demand from us. This means you can now keep stepping into code beyond when you get to DataAdapter.Update() for instance and trace all the way down the stack.  This is going to make it a lot easier to dive deep into debugging to see what is really going on when you hand off a bunch of parameters to a method in the .NET Framework.  I can think of a number of times this would have been incredibly helpful in tracing down those "oh, I should have set parameter x to something that could have been cast to a y"

    I'll be doing a channel9 video today or tomorrow, any questions for the team, let me know!

Page 1 of 1 (4 items)