Apps are perhaps the biggest change between SharePoint 2010 and 2013. But how ready is the App Model? Is it even worth spending the time learning it, and if you do learn it, what is the best, clearest way of making it stick inside our minds with 100-percent clarity on what works? More importantly, what doesn't work? This course "uncloudifies" this cloud-ready technology.
Sahil Malik has been a Microsoft MVP for the past 8 years, author of several books and numerous articles in both the .NET and SharePoint space, consultant and trainer who delivers talks at conferences internationally.
Sharepoint Apps Introduction Hello everyone. My name is Sahil Malik, and in this video, I'll be talking about SharePoint 2013 Apps. In this series of videos we'll start with a crawl-walk-run approach. We'll start with the basics, and then we'll keep diving into deeper, and deeper, and my aim here is to give you a good practical insight into why Microsoft created apps. Are they any good? Or bad? And we'll get a pretty good balanced approach and view on the limitations of the platform as well, and I also like enough hands on experience to see what is it like writing an app, deploying it, maintaining it, upgrading it, and so on and so forth. So, without much further ado, what have we covered so far? So far, everything that I've talked about on my various videos on Pluralsight about SharePoint 2013 have been about SharePoint solutions, WSB files, farm solutions, or sandbox solutions. Farm solutions that were introduced in SharePoint 2007, they worked in 2007, 2010, 2013. Sandbox solutions were introduced in 2010. They still work in 2013. Everything that I'm talking about is also covered here in my book in SharePoint 2013 Planet of the Apps. This is available on Amazon. com. I've pasted the link up there for you, sp2013apps, bit. ly/sp2013apps.
Writing Apps Using Visual Studio Hello everyone. My name is Sahil Malik, and I'm very pleased to be talking about this next video, which is writing your first Visual Studio app, and by app I mean a SharePoint app. So, in the previous video, I covered some basics about SharePoint apps, and in this video I'm going to further that discussion by taking the example of what is the simplest possible SharePoint app, which is a SharePoint-hosted app. Now the SharePoint-hosted app I'm going to write, first basically start with a crawl-walk-run approach, we'll start by writing it in a simple app that runs full screen. We'll understand how Visual Studio packages it and deploys it, how would you do in production, how things work behind the scenes, things like permissions, tokens. The idea is to get enough understanding about SharePoint apps, and once we start diving into the murkier waters of provider-hosted apps, all of these concepts that will be clear to us by then, we'll easily be able to apply them to provider-hosted apps.
Client WebParts and Custom Actions Hello everyone. My name is Sahil Malik, and in this video I'm going to be talking further about SharePoint apps, and so far I've talked about basics of SharePoint apps, golden rules, etc. We saw how you can write a SharePoint-hosted app using Visual Studio, how you can package such an app, how you can deliver such an app to your IT ogre so he can deploy it. And next we're going to talk about a concept called as Client Web Parts and Custom Actions. And remember, everything that I'm talking about here is applicable to both SharePoint-hosted apps, and provider-hosted apps. So, both SharePoint-hosted apps and provider-hosted apps can work as client web parts, and can work as custom actions. But it's easy for me to demo that using SharePoint-hosted apps, so first we'll solidify our understanding using SharePoint-hosted apps, using client web parts, and custom actions with SharePoint-hosted apps, and I think you'll find it very easy to extend that knowledge to provider-hosted apps.