Summer is over, slacking time is over, it's time to get up to speed and learn some new stuff. There's very much to talk about this fall if you're interested in SharePoint. And this fall I will do a couple of conferences as a speaker, which I very much looking forward to.
TechDays 2016, Amsterdam
For the first time I will attend and present at the TechDays 2016 in Amsterdam, the 4th and 5th of October. A local conference hosted by Microsoft. I will present three sessions:
- Introducing the SharePoint Framework
- Deep dive building client-side Web Parts using SharePoint Framework
- SharePoint Futures - Christmas came early this year!
The SharePoint and Office 365 track will be outstanding with where you also can listen to Waldek Mastykarz and Albert-Jan Schot.
SharePoint and Exchange Forum, now SEF Unity Connect
I don't know for how many years I've done this show, SEForum, 26th to 28th of October. It's the best conference for SharePoint, Office 365 and Exchange in Sweden, the Nordics, Scandinavia. And you'll find all the experts here, such as Spencer Harbar, Eric Schupps, Jesper Ståhle just to mention a few. This year I'm honored to do the keynote, together with Dan Holme (Microsoft). It will be a blast! And I will also do the following break-outs:
- Building Modern Solutions with the SharePoint Framework
- SharePoint as an Intranet
If you're planning to attend, please use this code SEFWICW10 to get 10% off!
If you're around, come by and say hi, looking forward to meeting you all out there on the road.
Today is the day many of us have been waiting for since the big SharePoint event at May the 4th. The highly anticipated SharePoint Framework (SPFx) is here and announced in at the SharePointFest, in this blog post, as well as in the new Github repo for SharePoint. Personally I've been waiting for this even longer after being involved by the product team to give early feedback and also attending the first top secret DevKitchen "hackathons" where we could try out very early bits.
The first release of many to come…
This is the initial public preview release, officially christened the SharePoint Framework Developer Preview, is a beta, maybe an alpha, of the SharePoint Framework. This is by no means something you should use or deploy to production. Things will change! Period. There are several known issues at the moment and some of them will likely incur breaking changes. But please, build stuff and give feedback to the product team, use the Issues feature in the Github repo.
This initial release focuses on client-side Web Parts which can, once released, be used in you classic SharePoint sites and pages as well as in the new modern user experience that is slowly being rolled out throughout the suite. As some of you know, I've spent quite some time on Web Parts and written a book on the topic, so this is something that gets me really excited.
How and where to get it!
All you need to do to get your hands on it is to follow the instructions on the Github repo. I'm sure we'll see tens and hundreds of blog posts on how to do it, but I recommend you to follow the one in the repo to start with. And, if you can't follow it, create an issue, make a pull request with an update - make sure we get good official documentation! Heck, I'm pretty sure I will write a couple of posts on the topic, but I will also continue to provide feedback on the framework and the documentation.
You will find samples, documentation and all you need in a set of brand new repositories in Github, also under a brand user/organization called…SharePoint (yes, no more generic Office dev, SharePoint is back!).
- SharePoint organization at Github, the main source for all your SharePoint Framework details - https://github.com/SharePoint
- SharePoint Framework documentation
- SharePoint Framework API documentation
- Office UI Fabric - the React edition
Need to know more?
Keep the conversation going on Twitter, SharePoint Stack Overflow, the new Office 365 Community network and other social media, and do use the #SPFx hashtag. I'll try to hang around at the SharePoint Stack Overflow as much as possible, since that is the best platform of the above mentioned ones.
I've previously written a Q&A on SharePoint Framework and will continue to update that post with details and changes in the current preview release.
Now, go, build something awesome!
Here's one of these real life stories that caused some headache for quite some time but was in the end very easy to resolve. I'll write it down and hopefully some of the search engines pick it up and help some other poor soul out there.
We have a solution that uses publishing pages to manage news articles and information pages in SharePoint Online. These articles and pages have a custom page layout with a custom content type, so they look decent and have proper metadata. They are all deployed using the PnP PowerShell cmdlets.
Creation of pages worked flawless and the rendered nicely. They page layouts use jQuery, some Office Fabric components (including those nasty jQuery scripts for that).
So far so good!
We wanted to roll up this News articles through a custom Web Part based on a search criteria, and also show some of that metadata, such as News category, rollup image and more. But the pages was not indexed. First thought was that well, indexing in SharePoint Online usually takes everything from a couple of minutes to a couple of days, so just wait. Then summer vacation came - I'm not complaining - and when i got back we had index. Ok, good. But then I started adding some custom managed properties to the rollup feature and was waiting for it to pick up the changes. I clicked re-index the libraries, I clicked re-index the site, added new pages and articles, I might even sacrificed the cutest little kitten you can imagine - but nothing. The pages and articles was just not picked up by the crawler. So I started to smell something fishy.
Is there something wrong with my SPO tenant? No, same issue across multiple tenants!
Can it be the page layout? No, it renders perfectly in all browsers!
Can it be the PnP PowerShell cmdlets? No, the same issue if I uploaded page layouts manually!
First of all I added the CrawlTime managed property to see when stuff was actually crawled and that there was nothing wrong with the crawler. I could see how this managed property was populated on other stuff than the pages. So there is obviously something wrong with our pages and not SPO.
Time to get my troubleshooting gloves on and I brought out my checklist for this. Since I can't check trace logs (ULS) in SharePoint Online all I could do was to inspect the crawl logs. And now I could see in plan text that my news articles could not be crawled:
"6074070", "https://contoso.sharepoint.com/news/Pages/xyz.aspx", 755", "Item Error", "The SharePoint item being crawled returned an error when attempting to download the item. ( SearchID = F2A4A5E4-AAAA-AAAA-B034-10C593EF6CCE )", "8/4/2016 7:07 AM", "https://contoso.sharepoint.com/", "Intranet",
So, the crawler can obviously not download my page! I also noticed the following cryptic error message on the site and library levels:
"755", "Container Error", "The SharePoint item being crawled returned an error when attempting to download the item. ( Unknown Error The surrogate pair (0xD8DA, 0x272) is invalid. A high surrogate character (0xD800 - 0xDBFF) must always be paired with a low surrogate character (0xDC00 - 0xDFFF).; SearchID = 00D32C87-7CD9-4350-AFF4-BBF38B8EB712 )",
Hmm, some Unicode errors?
I was out of options and I could not do an IISRESET (Rule #3) - so I called a friend (Rule #4), Doc Hodgkinson. He was almost as clueless as I but asked my to test it on a normal SharePoint 2016 on-premises installation (born in the cloud you know) and see if I could replicate the issue and also then have the option to check for more detailed crawl and trace logs.
And so I did. I ran the installer on a clean SharePoint 2016 install, started creating a page using our custom page layout and BOOM! The browser just went white!!! Nothing! It rendered fine in SharePoint Online (cloud-born innovation!)
Quickly I opened up the trace logs and reloaded the page and found this in the logs:
SharePoint Foundation General ahi1s Medium Cannot find requested file: 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\Template\layouts/https://code.jquery.com/jquery-2.1.4.min.js' SharePoint Foundation Upgrade aq775 Unexpected CannotMakeBrowserCacheSafeLayoutsUrl ArgumentException: 15/0/1033/https://code.jquery.com/jquery-2.1.4.min.js
Aha! The Page Layout contains a ScriptLink control that points to that CDN location.
I quickly changed it to a normal script tag and the page rendered fine in the SharePoint 2016 on-premises instance, and I uploaded it to SharePoint Online where it also rendered fine. And…after just a few minutes all my articles was indexed and queryable and I had my Managed Properties. And all was good!
I find this bug very interesting, SharePoint Online obviously accepts full URLs in the ScriptLink property when rendered through a browser but when the crawler sees it something weird happens (also, I wonder why it gets Unicode errors on the site and library as well). Also, the code for ScriptLink is different for SharePoint Online and SharePoint On-Premises (I have NOT tested all CU's though). Also, it's really weird that it some time during the summer actually indexed the pages.
All in all, actually using an on-premises installation for troubleshooting my SharePoint Online issues was a great idea (big thanks as always Neil) and I'll keep that option as a part of my normal routine from now on.
I have long thought that GUIDS are unique, well GUID actually stands for Globally Unique Identifier. And SharePoint is one unique product using GUIDS everywhere. There are 2^128 possible GUIDs to choose from, so there should be no need to reuse GUIDs as long as I'm alive methinks.
SharePoint uses GUIDs to uniquely identify Site Collections and Sites, and more, and this is for instance exposed through the ID property of the SPSite and SPWeb objects. If you take a look at the documentation for SPWeb.ID it actually says: "The globally unique identifier for the website" - which I interpret as this ID is unique, globally! Period.
When you create a Site Collection in SharePoint you create a new Site Collection (SPSite) and a Root Web (SPWeb). The SPSite will be given a unique identifier, a GUID, and so is the root web as well. Due to the way the API is created you cannot find a web directly using the unique Web Id, you actually need the Site Id. Even so there are multiple applications and services that has only stored the unique Web Id and used that as something unique.
Given (recent) changes and a new feature called Fast Site Collection Creation, used in SharePoint Online and to some extent in SharePoint 2016, this is no longer true and you can no longer trust in the Web Id being unique. When a site collection is created with a root web, specifically the SharePoint Team Site (STS#0), it is copied from a site master. The Site Collection is given a new GUID, but the GUID for the root web is copied from the site master. So, in SharePoint Online all your Site Collections with a root site of type Team Site will have the same id.
There is no workaround for this, you cannot change the Id - your only chance is to use a combination of Site Collection Id and the Web Id. That is a dual GUID combo - can't be more unique than that.
Some of you perhaps already knew this, some not. Hopefully you'll be aware of it now and I wish this would be different and that the Fast Site Collection Creation actually updated the Site identifier property, and since I most likely cannot have that I wish the documentation would be updated with a hint on this.
This is by no means an official support statement from Microsoft, rather an unofficial compilation of official statements.
Last week the SharePoint Online team rolled out the preview of the Modern SharePoint lists. Modern Lists are the new incarnation of ye ole Classic SharePoint lists that we all loved and hated over the last decade or so. The Classic SharePoint lists and libraries has been one amazing and powerful tool and I would say that they have been a big part of the success SharePoint has had. Customizations using XSLT, SharePoint Designer and JSLink has all contributed to its success.
The new Modern Lists (currently in preview, not even in First Release and you need special voodoo tricks to get it to work) does not support these kind of customizations, for now. Over the last week or so I've heard large cries and worried Tweets about all peoples current customizations. Microsoft has not been overly clear on the supportability for classic lists in public writing but rest assured; Classic lists will be here as long as they are used and needed. This is what I've been told by the team and what they are trying to say;
- "We have no plans to remove classic mode anytime soon"
- "We heard your feedback on extensibility and customization in particular, and we’ll have more to share in a future update. We plan to add support for customizing the page using modern techniques. Until then, customized library pages should stay in classic mode."
- "Classic mode supports your customizations today, and tomorrow."
- "In the meantime, it’s important for us to maintain continuity for our existing customers. "
Also I do think it is good that they don't set a date for supportability, which some people request, like they've done with for instance InfoPath. If they do that, they have to support Classic Lists until that date. I think it is better they make great progress in making us move to Modern Lists as soon as possible, and when they see no or minimal usage of Classic Lists, they can remove it. The same as they've done for Sandboxed Solutions - something we known coming for years! [Update] But yes, I do think a notification a little bit more than 30 days prior to shutting it down makes sense, if and when the feature gap is closed.
So, keep calm and continue to use your classic lists - however start planning for a modernization of your XSLT List View Web Parts, your JSLink customizations and more. I know that what's coming to replace these, will be much more interesting and be way more modern.
As many of you have noticed I have not been posting my What's new on the Office Roadmap updates. Well, I've been on a vacation not trying to think of Office 365 to start with, and then also, I'm ending my series of these posts. Sorry.
I have to start with saying that I love the amount of changes we see now in the Office 365 service. The team(s) is/are doing an amazing job with kicking out new features and updates in some areas. Our favorite SharePoint is killing it with features at the moment, and more is to come. And do believe this will continue for the foreseeable future.
Why? Why, do you do this? There's plenty of reasons for me ending this series. It's been going on now since March last year (which is way longer than I expected) and it was exactly 50 posts! So plenty of updates has been going on.
First of all it still takes me humongous amounts of time compiling each post, figuring out what's changed, what each change actually means, filtering out false changes, going back to my old change posts, coping with errors in the changes etc etc.
But most importantly the reason I stop doing this is that the Roadmap does not really reflect the changes going on (yea I know, Roadmap and changes are not the same). Using the Roadmap as a guide on what's to come is not that accurate that I hoped, sorry. And the #1 reason that I started this series was to get the Office 365 team to understand that we need a Roadmap where one can see changes, one that you understand the changes and one that you can trust, otherwise there's no point! There's no point giving you examples, there's to many. After a year and half very little has happened…
I'm going to miss it though. I've had some fantastic online and offline support of these posts and I enjoyed adding some personal touch to my "analysis". Some liked it, and some despised it to the extent that I'm actually persona non grata in some "communities". I'm probably to close to the truth and far to many people have hard to understand irony…
Nevertheless…if you still want to find out what's happening on the Office Roadmap site, the PowerShell script I had scheduled is available as a Gist on Github.
Thanks for all the support!
Happy Friday and welcome back to another Office Roadmap update. This time the day before the big SharePoint Saturday, here in beautiful Stockholm, where we all are going to indulge on the goodness that was announced a couple of weeks back at the SharePoint Futures event.
Lot of new stuff in the mobile space this time around.
- Windows Universal App: OneDrive UWP (Universal Windows App) are now launched and live (new)
- User Activity Reports: Compliance center improvements for OneDrive/SharePoint on document views/edits/downloads etc (from in development)
- Intelligent Discover for Android: Discover (Office Graph) view in the Android OneDrive app (new)
- Mobile Access to SharePoint Online for iOS: Access your SharePoint files from the OneDrive app (new)
- Office 365 Groups: easily add users from a distribution list to a group: this is cool, now you can add all members from a DL to an O365 Group instead of one user at a time (new)
- Self-service NGSC setup and goove.exe takeover: Simplified setup for NGSC (Next Gen Sync Client). Finally. Goove.exe (giggles) (new)
- Office 365 Groups: scripts to migrate Distribution Lists (DLs) to Groups: Some sweet scripts for migrating DL's to O365 Groups (new). Funny it's listed as rolling out, the script is there! What's missing.
- Project Online - Developer Samples: Project Online goes Github: http://aka.ms/pppmapisamples (new)
- Project Online - OData performance improvements: and when they have some sample code, they of course want it to perform (new)
- SharePoint home in Office 365: the new SharePoint Home tile is being rolled out. Check /_layouts/SharePoint.aspx in your tenant. (from in development).
- Office integration added back to NGSC: improved office integration in the NGSC (Next Gen Sync Client) (new)
- Improved image attachment viewing in Outlook on the web: Always nice to see improvements to the web client, it's now way ahead of the desktop one, this time big thumbnails and side by side view (new)
- Annotating and inking for Mac: Draw using your mouse on you Mac - cause you suck and don't have touch on that shiny thing (new)
- Copy and move to SharePoint:
- Intelligent Discovery for iOS: Discover (Office Graph) for the iOS OneDrive app (new)
- Intelligent Discovery for Windows Phone: Discover (Office Graph) for the Windows Phone OneDrive app (new). Anybody want to buy a couple of Lumias, I have several as paper weights.
- Mobile Access to SharePoint Online for Android: Access SharePoint files and not only OneDrive on your Android OD4B app. (new)
- Mobile Access to SharePoint Online for Windows Phone: Access SharePoint files and not only OneDrive on your WP OD4B app (new)
- Office 365 Groups: Exchange Admin Center (EAC) UI for migrating Distribution Lists (DLs) to Groups: Evolution of the migration scripts mentioned above. You will soon be able to migrate from DL's to Groups using a single button in the Exchange Admin Center. Nice! (new)
- OneDrive for Business Shared folder Sync: this is a nice new feature. If someone shares a folder with you from their OneDrive you will be able to sync them (new)
Hey, happy Friday the 13th! Here's a small Office Roadmap update for all of you Jason fans!
Not that many changes this time around, but still interesting, and a lot of Outlook 2016 for Mac releases.
- eDiscovery Case Management, Hold & Permissions: the new eDiscovery features are now fully rolled out (from in development)
- Enter full screen view in Outlook 2016 for Mac: the full screen view for Mac Outlook as announced in January are now out. (new)
- Find a meeting room in Outlook 2016 for Mac: and so is the possibility to find a meeting room on your Mac (new)
- Office 365 Groups: ability to update privacy type: you can now as a Group owner change the privacy type of your Groups (public or private) (from rolling out)
- One-click Archive: The on-click archive feature in Outlook on Mac are now also fully rolled out (from rolling out)
- Outlook 2016 for Mac two step authentication: And you can also log in using two factor authentication on your Mac (new)
- New editor for Outlook 2016 for Mac: And if you're lucky you might even be getting the new editor in Mac so you can use "more fonts and colors". (new)
- Project Online - Removing the upper limit on number of PWA instances per tenant: after this update you will be able to have unlimited number of PWA instances, was previously only 7. (new)
- Right to Left language support in Outlook 2016 for Mac: and if you write your stuff from right to left you can now use Outlook 2016 on your Mac, without writing backwards (new)
- FastTrack | Dropbox to OneDrive for Business Migration: If you are using Dropbox you can soon get help from the FastTrack center to get yer files out of there (new)
- New usage reports for SharePoint, OneDrive and Mailbox Storage: the new admin UI will get better and improved reports for storage usage in SharePoint and Exchange. (new)
- Office 365 Usage Reporting APIs: and not only that, you can suck that data into your own apps as well (new)
- SharePoint mobile app for iOS: Nothing new here, it's just a rename from "The new SharePoint mobile app" to "SharePoint mobile app"
The Office Roadmap updates with the new announcements from the Future of SharePoint event has arrived (they arrived May the 4th to be precise). I'm back from the event and San Francisco and I'm full of the energy that the SharePoint team transmitted.
You should specifically take a look at the In Development part here. That's where we got the new and fresh stuff from the Future of SharePoint event.
- Delve Analytics: Do you want all the details on how and when you work Delve Details and an E5 subscription is all you need (from in development)
- Drive Shipping and Network Based Data Import for Office 365: Fast Track is getting more and more mature with import options (from in development)
- FastTrack | Box to OneDrive for Business Migration: Still using Box? Get your files over to OneDrive with Fast Track (from in development)
- FastTrack | Expanded language support: More languages available in the FastTrack (new)
- FastTrack | Power BI onboarding support: And Fast Track Power BI is now live (from in development)
- Multiple timeline bars in Project Online: This must be one of the features that's been jumping back and forth the most on the roadmap (from rolling out)
- Office 365 Groups: multi-domain support: This is one of the most important feature releases of Groups. Read this article for full details and configuration options. (from in development)
- Office 365 Reporting Dashboard: Better reporting in the admin center (from rolling gout)
- OneDrive for Business Recent Files to Sway: Easier access to your OneDrive docs in Sway (from in development)
- Skype for Business App SDK: Get your coding skills on and build some Skype Apps (from in development)
- Skype for Business Mac Preview 1: The long awaited Skype Mac client is not out. Feedback on it has been moderate at best though (from in development)
- Updated people profile experience in Office 365: The Delve profile page is now fully rolled out. I wonder if Delve will stay as the document discovery feature or if it just will be renamed to "My Profile" or "People" or something, which would make total sense(new)
- Yammer user profile update from Azure AD: The one-time sync from Azure AD is now launched. Wonder if we ever will see a proper sync? (from in development)
- Basic Chat: Basic Skype chat from the Skype icon in mail - it doesn't say that it's web based, but I guess it is(new)
- Office 365 Groups: usage guidelines: A very important update, this allows you to modify the usage guidelines for Groups (another feature copied from Yammer) (from in development)
- SharePoint Online - modern document library experience: The new doc lib experience, mayhaps rolled out a bit early and without any guidance (new)
- eDiscovery Case Management, Hold & Permissions: more permissions control for eDiscovery and compliance stuff (from rolling out)
- New AutoCAD file format support in Visio: AutoCAD file support in Visio… (from rolling out)
- Office 365 Groups: search Groups files using Office Delve: Searching should now show documents from Groups (new)
- SharePoint home in Office 365: Finally Office 365 and SharePoint will get a proper home page. The Sites tile will be renamed and now point to this page. You can read more about this feature here. (New)
- SharePoint Online – Client-side Web Part for Existing SharePoint Pages: The new customization features announced at the Future of SharePoint Event. Client-side Web Parts created using the new SharePoint Framework on existing SharePoint pages. Read my post about it here (new)
- SharePoint Online - modern lists experience: A new lists experience, very similar to the new doc lib experience. A great and modern looking UX. (new)
- SharePoint Online - SharePoint Framework: The new client-side framework that will be used to make the future customizations and development of SharePoint. This is the Framework that Microsoft will build the new "NextGen" portals and the one we will use. There's much more to read about this here. (new)
- SharePoint Online - Site activity and insights on the Site Contents page: Each site will get its own set of statistics that shows you how the site is used and what activities are going on (new)
- SharePoint Online – Webhooks on SharePoint Document Libraries: One of the first new extensions to the SharePoint APIs. I'm glad they are using standardized Webhooks, instead of some weird remote event receivers. Hopefully we'll get the same for lists (new)
- The new SharePoint mobile app for iOS: Announced as the "Intranet in your Pocket". The new SharePoint App will first come for iOS (actually I'm already using it) and then later for Android, and if Windows Phone is still alive by the end of this year those two users might get it as well (new)
- Class Notebook: limit sharing and deletion of section groups: This is just weird, this was rolled out the other week and is now all of a sudden cancelled (from rolling out)
At the Future of SharePoint event in San Francisco on May the 4th Microsoft announced the new and improved customization option and/or development model called the SharePoint Framework. This is a development model that solely focused on client-side development. There's been some confusion going on on Twitter and other social medias and podcasts and I thought I should put together an Q&A post for this.
This Q&A post is totally unofficial, all of this is currently in private preview and some comes from my (awesome) DevKitchen experiences, so things can and will change and I take no responsibility of any errors in this post or any financial, physical or mental issues caused by reading this.
I will try to keep this post alive as much as possible and if you have any questions, feel free to post them and we'll try to get answer to them. I also listed some questions, that I do not have an answer to, but are working on to find out…
 Updated 2016-08-17, after initial developer preview release
Q: Is the SharePoint Framework an new development model
My point of view here is that this is not a completely new model. The framework might be new, but that is a framework that we all has been longing for for quite some time. Client-side development has been here for years and we all built our own frameworks. Now Microsoft is creating this framework for us, it is standardized and they will also build in native support for this framework in SharePoint. This model leverages techniques we are used to such as CSOM, the SharePoint REST API's, the Microsoft Graph etc and at the same time embraces open source technologies such as node.js, Gulp, Yeoman and more.
This model does not deprecate anything; if you need to do full trust code you can still do that (on-premises) and build WSP's, if you want to use the App/Add-in model you are free to do that.
Q: What's not so new in this model?
A bit of a weird question, but I wanted to highlight that this model actually piggy backs on previous development models and infrastructure in SharePoint - specifically the Add-in model. The packaging and deployment mechanism is using the add-in model. The solutions built using the SharePoint Framework are being packaged as a .spapp file, which is very similar to the .app package created when building a SharePoint add-in, and distributed using the App Catalog.
Q: Are the Feature framework, Sandbox and the Add-in models dead?
[Added 2016-05-08] Far from it! The Feature Framework (introduced in SharePoint 2007) is very much alive for on-premises deployment and is in many cases a requirement, with the caveat that it is hard to convert that to a model that works in the cloud. The Sandbox is partly dead, it is, code based Sandboxed solutions are officially deprecated, but there are still a usage for declarative Sandboxed solutions. The Add-in model is also still a very relevant way moving forward; Add-ins offers features that the SharePoint Framework doesn't (such as isolation, elevation of privileges etc).
Q: Does this replace Add-ins?
[Added 2016-05-08] No! The SharePoint Framework will NOT replace Add-ins, the will co-exist side by side. There's no need for you to migrate your Add-ins to the SharePoint Framework. That might not even be possible to do - since you want to stay in isolation, you might want to elevate privileges, you might want to do work without user interaction, you might want to use the existing store.
Q: Do I need to create those weird app keys and secrets and learn all about OAuth?
[Added 2016-05-08] No, this is not how the SharePoint Framework works You only run this as a user, within the SharePoint page context so you are already authenticated and the SharePoint Framework app are already authorized with the currently logged in users credentials and permissions.
Q: Can I call the Microsoft Graph using the SharePoint Framework?
[Added 2016-05-08] No. Not now at least. You don't get any token that you can pass to Microsoft Graph (graph.microsoft.com). The only API's you can access are the same ones as you can using any Script editor web part or script embedding. If you really want to query the Microsoft Graph, you need to create an Azure AD App and sacrifice to the gods that the Azure AD team fixed ADAL/MSAL so that it works with Internet Explorer and trusted/intranet zones, and do it the "old fashioned way".
Q: Is there any specific requirements on my infrastructure?
[Added 2016-05-08] No, there is no requirements on app-domains etc. as we have in the Add-in model. You can host your SharePoint Framework solutions on any web server anywhere or in SharePoint itself, without any extra infrastructure components. This also makes it very easy for the SharePoint team to bake this into a future Feature Pack (see below).
Q: What does the .spapp package look like?
When you package your client-side solution, an .spapp package is created. This package looks very similar to any other SharePoint Add-in you're creating. This package contains the following major things:
- An AppManifest - a regular SharePoint add-in AppManifest with the difference that the App element has a IsClientSideSolution="true" attribute
- One or more features - a normal Feature element file
For client-side applications it is a bit more complex as they are tied to lists. For the sake of uncertainty I leave that description out for now (well I got to have a reason to lure you back here). I know there are discussions on how this should be implemented/executed.
 Note that client-side applications is not part of the initial release.
(Once again this might very well change over time when we get closer to release)
Q: How do I deploy my solution?
You have three options of hosting all your files:
- For Development you host your files locally (localhost using the node.js express engine) and can take advantage of automatic reload of your app when you save files etc.
- You can deploy to a SharePoint library. A good option if you want full control of the artefacts in your tenant
- To a CDN. This is most probably the best solution for ISV's where they centrally can manage all the artefacts.
Q: How do I update a client-side solution
Q: Will the Office Store allow client-side solutions built using the SharePoint Framework.
Thank you, very good question. I do not have an answer to this right now, but I assume that the team are working hard on this, specifically regarding the topics around updates. To be continued…
Q: But hey, I'm an ISV and this looks like an Enterprise developer feature only!
[Added 2016-05-08] Thank you for asking and noting. Yes, I agree that the current initial release is focused on enterprise developers. I know one of the goals with this new framework is also to support the ISV market. I have however no timeline for this.
Q: What about isolation in my customizations
No problem! Then you just encapsulate your "secret" business logic or algorithms in web services and make sure that those are CORS enabled.
Q: What client-side frameworks are supported?
All of them. Well, I haven't tested all of them, but that's the idea. The product team does not want to limit you with what frameworks to use, so go ahead use your preferred ones. Personally I've built client-side solutions with jQuery, Angular 1.x, Angular 2, React and Knockout.
 Microsoft and the Product Team for SharePoint has taken a decision to use React in their solutions. This actually have a big effect on us developers. For instance the new Office UI Fabric version 2 - is React only! So if you want to use the new components offered you either have to use React in your client side solution or reverse engineer Office UI Fabric, since there's no "pure CSS" spec/implementation.
Q: Do I really need to learn TypeScript?
Q: Do I really need to use Visual Studio Code?
Short answer; absolutely not! You can use whatever tool you want to write the code. However I guess most of the demos and instructions from Microsoft will be based on Visual Studio Code.
Q: But I really want to use Visual Studio that I'm used to and love so much!
Yea, I'd love that option to and there's a lot of benefits of using Visual Studio. I know that the product team are aware of this and I'm pretty sure that they are working on it. But see this as an opportunity to learn Visual Studio Code meanwhile… Visual Studio is fully supported, together with the use of the Node.js tools for Visual Studio (NTVS). Please use at least version 1.2!
Q: Do I really need to use Gulp?
Short answer: Yes. The current tooling is built on Gulp tasks and I recommend you to start with that. But if needed you can configure and modify those tasks. It is also totally possible of building your own package mechanism and code structure that fits your style of coding, if you have the time. (I actually wrote my own package mechanism and gulp tasks from scratch just to understand how it all worked out and to be able to give feedback to the team - so it is possible)
Q: Does it work on my bestest device ever - my precious Mac?
[Added 2016-05-08] Yup! Use Visual Studio Code on your Mac, use whatever text editor you like, use it on a Linux box! This is one of the reasons the team choose to use Node.js npm ,gulp and Yeoman as the foundation for the development framework and that is why the go with Visual Studio Code first (instead of the full Visual Studio).
Q: Do I really need to use Git?
Short answer: Nope! Git has nothing to do with this, at all. But the code samples and the source for all the tooling will
most likelybe distributed using Git/Github so if you're interested in contributing you should learn it.
Q: Is this Open Source?
[Added 2016-05-08] From my understanding the idea is to have this Open Sourced once we get out of "closed beta". There really is no point in doing it any other way with client side components,.
Q: What is the Workbench?
The Workbench is a test rig for client-side solutions which comes in two flavors. One static html version that are used without the context of SharePoint. It is capable of rendering the page canvas and client-side solutions so that you can work with the UX components. If you need live data however you need to create mock data for your domain model. The second flavor of the Workbench is the one running in SharePoint, with that one you have access to the full page context including SharePoint data.
Q: What about SharePoint 2016 on-premises, will we ever be able to take part of all this?
Yes, I do believe so. There's nothing in here that actually locks this model to Office 365 and SharePoint Online and at the Future of SharePoint event there was announced that SharePoint 2016 will get "Feature Packs" during 2017. So, yes, this will most likely happen. Microsoft is targeting an on-premises release of the SharePoint Framework for the first half of 2017. This will be a part of a feature pack for SharePoint 2016.
Q: When can I get my hands on this??
[Added 2016-05-08] It was announced at the Future of SharePoint event that this will roll out starting this summer to first release tenants. My guess is that we will have a first version by the end of this year (2016). You can get your hands dirty right now over here:
Q: Is it SPX or SPFx?
Over the last two days I've seen the SharePoint Framework been shortened both as SPX and SPFx. I prefer the latter one. How about you?
Q: What permissions is needed to deploy a SharePoint Framework app?
[Added 2016-05-10] A really good question. This is an assumption based on the experience so far. You distribute the app/solution to the App Catalog - so you need to have permissions on the App Catalog.
Q: How does the development life cycle look like?
[Added 2016-05-10] The development life cycle is one of the things that this SharePoint Framework would like to align with the rest of modern web development. You have multiple options and how you actually do it is up to you. This is how I see it and what works great with the tools:
- Build and host your solution locally (node.js Express web engine) using the local Workbench, without any real SharePoint data just using mock objects
- Host your solution locally as above, but deploy the solution to the app catalog and then add it to a site so you can test it with real data
- Iterate 1 and 2 until you are happy
- Package your solution, now pointing to the CDN location, and upload that to the App Catalog to distribute it to a SharePoint tenant
- Repeat 4 and 5 in dev, stage or production
- Go back to 1 to build your next version/update
Do you have any more questions? Let me know!