An Orcas Question…
So far, I've told you that we're planning new Technology Specialist certifications around the 3 main technologies in the .NET 3.0 stack. Actually, because both the complete technology solutions and the exams will be released in the Orcas timeframe, these new certifications will roll up under the .NET 3.5 banner (I know – the whole new versioning strategy – yea – I get it…). Anyways, because we are going to be releasing in the Orcas timeframe, there are several additional technologies that will be available. Some of these technologies include language enhancements such as extension methods, lambda expressions, anonymous types, object initializers, etc… Therefore, my question to you is as follows. What are your thoughts around doing a .NET 3.5 foundation exam as a prerequisite exam to all of the other .NET 3.5 TS exams – much like how 70-536 was a prerequisite to the .NET 2.0 TS exams? There are a few options as I see them.
- Create a TS-level exam which would cover the items mentioned above in addition to basic .NET FCL content (basically, the 536 content that actually *was* foundational – not GDI+ stuff, etc…). Make this exam a requirement for all .NET 3.5 TS certifications. The positive aspects to this approach, as I see them, are that a) we can focus the foundational content a bit better than we did in 70-536 and b) we can cover the new general features of the .NET Framework 3.5. The main problem with this approach is that it would require existing certification holders (folks who have already taken 70-536) to take another foundation exam. Now, let me say that I don't think that re-validating existing skills is necessarily a bad thing. However, I think it's problematic from a financial perspective – I would hate for existing certification holders to come away with the idea that such an exam was just another way to extract money from them.
- Do not create a new foundation exam around .NET 3.5 and make 70-536 as a prerequisite to all of the .NET 3.5 TS certifications. Since a majority of the new language features in .NET 3.5 were added in support of Linq, move this content into an ADO.NET certification path. The positive aspects of this approach are that a) we can leverage an existing exam and b) existing certification holders need only take the 3.5 specific exams (as they will already have passed 70-536). The problem with this approach is that there is potentially some confusion around version numbers (requiring .NET 2.0 foundation as a part of the .NET 3.5 certification).
- Do not create a new foundation exam around .NET 3.5 and do not require a prerequisite exam for the .NET 3.5 TS certifications. Since a majority of the new language features in .NET 3.5 were added in support of Linq, move this content into an ADO.NET certification path. The positive aspects of this approach are a) there is no bleed over of version number (see above) and b) there is only 1 exam required in order to achieve certification in .NET 3.5. The main problem (and this is big in my mind) is that new entrants are relatively unproven in terms of general .NET Framework skills.
Please keep in mind that the above in no way represents any formal plan. These are only my thoughts on the matter and I want to get them out there as soon as I can so that you can give me yours. It's always a relatively delicate balancing act to accommodate the needs of new entrants with the needs of existing certificate holders – and to complicate the matter slightly, I would really like to do that here without creating upgrade exams.
I look forward to your feedback.
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
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.