Microsoft MVP Logo

I will be teaching our (Critical Path Training) SharePoint 2010 Developer class in the Pacific Northwest and New England areas in the next 2 months. This five-day class, SPT2010 - Developing Solutions with SharePoint 2010, covers every angle for developers who are looking to learn the complete SharePoint 2010 offering. The class is targeted to .NET developers who may or may not have any experience with SharePoint. However those with SharePoint development experience (2003/2007) won't be left twiddling their thumbs... every module is engaging with what's new and great with the platform as well as the core SharePoint fundamentals (lists, libraries, etc).

Now is a good time to jump on the bandwagon and get your training. Why? While the class is delivered using the latest beta / release candidate release of SharePoint 2010, we're also offering registration at a special pre-RTM/beta pricing of $1,995 (regularly $2,995) until SharePoint 2010 reaches the RTM milestone. We're getting close to the RTM milestone with the recent news of the Office 2010 Release Candidate, SharePoint 2010 Release Candidate & Visual Studio 2010 Release Candidate!

The two classes Andrew has coming up on either side of the US are in the Microsoft facilities in Redmond, WA (February 22-26, 2010) and Boston, MA (March 22-26, 2010). If the links don't come across, you can get all the details you need at www.CriticalPathTraining.com.

So what's covered in this SharePoint developer class?

  • PowerShell, Visual Studio 2010 Developer Tools & SharePoint Designer 2010 (including extensibility)
  • Client side programming (Client OM, WCF Data Services), LINQ
  • Web Part Development
  • Sandbox solutions
  • Business Intelligence
  • Search Customization
  • Security fundamentals & claims based security
  • Business Connectivity Services
  • Workflows (Visio, SPD & Visual Studio 2010)
  • Enterprise Content Management & Web Content Management

Space is limited, so make sure you register early!

Technorati Tags: ,

Comments powered by Disqus