Microsoft can’t keep me quiet for much longer. I haven’t written about Dublin for many months, and I’m about to explode. Lucky for me we’re getting close to a public release, when I’ll be able to talk about features specifically and post new screenshots.
The first customers who will get Dublin bits are those who have been accepted into our TAP program. This is a great way for customers to get the technology early and a great way for us on the team to get early feedback about our product. See this page for more information and a pointer to how to apply for the program. By the end of the year we plan to release a public beta for everyone.
The themes of Dublin haven’t changed since I last wrote. Dublin is a set of extensions to the Windows Application Server role that make .NET 4 WCF and WF services easier to use. Some specific areas of focus are:
My role on the Dublin team has changed quite a bit since the last time I wrote. I started out as the “integration dude.” My job was to define core user scenarios, try them out, and give my feedback to the feature teams. I had a blast with that. It allowed me to get a good perspective of Dublin as a whole and to learn about all the feature areas. A few months ago I moved over to our Tools team. We’re the team that builds the IIS Manager and PowerShell features. I own some of the Monitoring features, specifically the raw tracked event view that you will use to troubleshoot problems with your services. Being on a feature team gives me the chance to go deep in a feature and help shape the product more directly. I’m having a good time with this and like getting my hands dirty.
But the team can’t keep me quiet. (Do you see the pattern here?). I’ll always have my end-to-end focus and big mouth. My big mouth turns out to be handy for demos and presentations, so you’ll still see me often act as the “demo monkey” for Dublin.
I want to hear from you. What questions do you have about Dublin? Which features are you energized about? Which ones need work?