What Are We Planning for .NET 3.0?
So this is a question that has come up a few times in recent history and after several conversations about the matter, I wanted to let you know what's on the roadmap. First, let me highlight the major takeaways from the discussions on our strategy.
- When talking about .NET 3.0, we are referring to the 3 major technologies that formed the API suite formerly known as WinFX (WCF, WPF, WF)
- .NET 3.0 describes a set of technologies. The professional level skills for building web and Windows applications (such as the skills for evaluating tradeoffs between performance and scalability, for example) remain relatively unchanged – at least in the near term.
- A technology specialist credential should be tightly coupled to a specific version of a specific technology. This most clearly identifies the specialty of the credential holder. It additionally aligns with the TS vision of tying the lifetime of the credential to the lifetime of the technology from a product support standpoint.
- While some of the .NET 3.0 APIs will eventually overtake the existing .NET 2.0 APIs in use – particularly WPF and WCF, this will not happen immediately, and the .NET 2.0 mechanisms for building applications are not going away for quite some time.
Therefore, here's the plan.
- We will plan to release between 2-3 Technology Specialist exams – each exam will yield a TS credential. We are still deciding whether or not we should group WF with WCF in one exam (hence '2-3'). You're feedback on this last point would be very useful.
- We are not planning on changing the professional level exams at this time.
- We will plan on developing new TS credentials for technologies (such as ASP.NET) that are affected as a part of the Visual Studio "Orcas" release.
So I know that there has been a lot of confusion surrounding the upgrade story into the new generation certs (more on that later). The good news here is that the upgrade story is simple – there's not one. Simply put, a Technology Specialist credential should assert that the possessor has a certain level of ability in using a specific release of a Microsoft technology. Therefore, you're never "upgrading" your TS credentials – just achieving new ones.
That said, the question of the professional level credentials is a little more complicated, but I think that I'll save that for another day.
Comment Notification
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using
Comments
Leave a Comment
About hdierking
I am currently the Editor-in-Chief for MSDN Magazine. I joined Microsoft in 2006 as a product planner with the certification team at Microsoft Learning. Prior to that, I spent my career as a developer and later as an architect. My main technology passions include pretty much anything on language theory, agile development, and service-oriented architecture.