Are you a traditional SharePoint developer used to working in Visual Studio on Windows building solutions or add-ins? On May 4th, 2016 at the Future of SharePoint event, Microsoft announced the new direction of SharePoint customizations: the SharePoint Framework. This development model not only favors the client-side approach to customizing & extending SharePoint, it’s the only approach that is supported. That’s a big change from the old ways that primarily favored the server side approach.
But that’s not the only big change; Microsoft also elected to make a big change in the development toolchain. Visual Studio is no longer the only or first choice if you follow Microsoft’s guidance. For the SharePoint Framework, Microsoft elected to go with the popular modern web development toolchain. While this toolchain is quite with web developers, it isn’t nearly as popular within traditional Microsoft camps… including traditional SharePoint developers. As such, it is not surprising to see so many traditional SharePoint developers have challenges and express frustrations in adopting this new development toolchain.
I’m one of those traditional SharePoint developers who goes back to the days before we ever had solutions… back when we were XCOPY’ing files to the server in SharePoint Portal Server 2003. But over the last few years, I’ve spent over half of my development life in this toolchain working with Node.js and NPM and these same tools we will use for SharePoint Framework development. In this email course, I will deliver a new installment each day to your inbox that will peel back the onion and simplify what may be confusing you. What can you expect? Sign up because the first day will introduce you to the course and explain what you will learn each day!comments powered by Disqus