Brian Loesgen's Blog

BizTalk Server, Enterprise Service Bus (ESB), SOA, Oslo, Dublin, WCF/WF... and related stuff!

  Home  |   Contact  |   Syndication    |   Login
  142 Posts | 0 Stories | 152 Comments | 81 Trackbacks

News

Tag Cloud


Archives

Post Categories

Image Galleries

My Blog Friends

As we head towards the PDC later this month, Microsoft today pre-announced some of the things you can expect to see there.

 

To meet the evolving needs of service-oriented applications, Microsoft is extending the capabilities of Windows Server, by adding a set of capabilities, "Dublin", aimed at making it easier to deploy, manage and monitor WF/WCF applications. For developers creating WF-based solutions, this is great news, because it means you will get an enterprise-grade runtime environment to host your WCF/WF. Prior to this, the only WF host from Microsoft was MOSS, you would have had to write your own host, which is a non-trivial task. Now, Microsoft has solved all those hard problems for you. If you're a BizTalk developer, then rest assured that you will get a host too that will run in this platform, and that all your investments are protected, BizTalk Server 2009 and the roadmap was announced recently, I blogged about it here.

 

I'm also excited about the enhancements to WF: workflows become declarative, and are XAML-based. You get a new flowchart workflow style. This is all building towards the future, and gets even more interesting with the  Oslo modeling platform. I'll have a lot more to say about that later, starting after PDC.

 

I'd also like to clarify something that may be, or could become, a source of confusion for you. There has been a subtle morphing recently of what the code name "Oslo" means. When there was just the vision, "Oslo" was used to refer to the entire spectrum of technologies that needed to be built to support the vision. Now that we are further along in the lifecycle, and bits are becoming real, those bits are naturally migrating towards what will ultimately be their ship vehicles.You can see some of that now, with the enhancements to WF/WCF that will be in .NET 4.0, and the process server capabilities that will be in the OS: these are things that used to be part of what "Oslo" was. So to be clear, when we say "Oslo" today, we are now referring ONLY to Microsoft's modeling platform. I like this shift, and it makes a lot of sense, although I find myself saying "Oslo and related technologies" a lot now when I refer to the whole vision.

 

Some early bits will be made available to PDC attendees, with betas to follow some time in the future. You can get an overview here. Steven Martin, Senior Director of Product Management in Microsoft's Connected Systems Division (CSD), wrote about it this morning here.

 

We're in for an exciting ride folks, this is just the start....

 

Technorati Tags: ,,,,
posted on Wednesday, October 01, 2008 5:49 PM

Feedback

# re: .NET Framework 4.0 and "Dublin" Announced 10/5/2008 5:08 AM Colin Jack
Interesting stuff, I see that "Duplex durable messaging" is part of the package and was wondering whether this is an enhancement/replacement to MSMQ?

# re: .NET Framework 4.0 and "Dublin" Announced 12/14/2008 6:37 PM Poor Developer
We are still working on .net framework 2.0 and are still not aware of even 3.5, we are having hard time to cope up with such frequent releases of tools and frameworks from microsoft. Each time the RAM and disk space requirement seems increasing. Our management is also not happy with such new versions coming in real short notice. We the software developers are forced to look into what is new, because they want to be sure that they are using the latest technology, but we have no time to learn new things, while we are busy in meeting dead lines of .net 2.0 and even 1.1 projects :)

Good luck!

# re: .NET Framework 4.0 and "Dublin" Announced 12/17/2008 5:25 PM Brian Loesgen
You’re actually not alone, a lot of companies and developers are in the same position. People out “on the edge” sometimes forget about the real world (yes, there are VB6 apps in production out there). However, the answer is simple: you need to demonstrate the value of a any new technology, the true BUSINESS value (how costs are reduced, efficiencies improved, margins improved etc). Once you show that, then the choice to embrace new and emerging technologies becomes an easy path to follow. I would never advocate uses the latest thing *only* because it’s new and cool (although I personally might use it :)), but try to stay aware of what’s out there. Armed with that knowledge, you may see a way to help you organization through the adoption of something new.

I think we, as an industry, are really on the verge of having some pretty major transformation technologies available to us. With that will come a lot of change, and new opportunities.


Post Feedback

Title:
Name:
Email: (never displayed)
Url:
Comments: