Notities bij: SharePoint Is Evolving: Your Customizations Should Too!

https://en.share-gate.com/blog/evolving-sharepoint-customizations?utm_medium=email&utm_campaign=SharePoint-Is-Evolving&utm_source=Sharegate

video

http://www.paitgroup.com
http://www.markrackley.net

Korte notities bij de video.

Tip: gebruik een custom action om een scriptlink naar jquery toe te voegen aan de master page. Een custom action die je maakt als sand box solution (no code). Dan kan je dit via een feature activeren en deactiveren voor een site collectie.

nieuw voor sp 2013: sp add-in model. Is an alternate approach for full trust solutions.

Bad thing. Moeilijk om te ontwikkelen, niet wijd verbreid, authenticatie is tricky, solution are surfaced using iframes (hello 1999)

script editor web part vs cewp: if you have a file (html) with script reference, css en js code. Put that file in a library and link to that file from a cewp. You can reference that script from multiple pages. You can then edit that one html file, and on all pages the changes are shown. You can do the same with a script editor web part, but when you change the html file, then those changes won’t be seen on the pages. You have to edit each script editor web part on each page. So use CEWP instead of script editor web part. For maintaining a script in one place.

sp2016 o365 : SharePoint framework: Client side web part.

In classic mode you can still use cewp. But in modern pages you can not.

• is modern client side development (beter debug experience, managed code etc)
• lightweght web and mobile
• used to build modern sp page
• backward compatible, support open source tools and js web frameworks
• Microsoft graph api coming soon
• open source tooling support react components, office uit fabric, yeoman, typescript, vscode
• spfx is in dev preview

 

skills needed

• js/html/css
• an open mind
• node, npm, yeoman, gulp?? (open source FTW)
• typescript
• office ui framework (front end visual framework, icon dialog boxes etc)