So , people that know me , know that I am no big follower for SharePoint tech. It’s always to slow and buggy.
From today’s review I got a few insights and a summary that will get you started if you’d choose it.
So my insights :
1). Playing with the open source – Microsoft desperately wants to play with the free world open source, that once was looked upon from above but now rule the coding development world. Thus Microsoft is forced to enter the open source market using new tools of development , yet again changing all that SharePoint developers previously knew.
There’s good and there’s bad
Good – the tech is being renewed , therefore staying relevant in some form. The developers will need to learn new tech and it will adjust them to the market outside the Enterprise they are in. Actually it can be a learning curve on account of the BIG MAN, because as I see it afterwards they can spreed their wings and fly.
Bad – the changes in tech each time throws off the development pace and make the learning curve annulled. The developers of SharePoint , generally usually working for Enterprise companies (specific type of guys), will need to readjust all they knew before. The dev is changed and modularized altogether using new different approaches as explained bellow.
2).The rule of 3-d version – The lecturers said about each minute that the API is not final and there is a need to be able to readjust each time the development to changes in the core development of Microsoft Team. He kept on and on complaining about his trouble adjusting the demo’s for the lecture two days before because “the Core code has been changed and nothing worked” – his words, not mine. I find it hard to believe that especially Enterprise companies will put at stake their entire back office system using this raw product.
As a summary my conclusion is
You can let your developers to work on some POC with new tech on 10%-20% of their time using “creativity time” hours and enable them to learn tips and tricks, but I wouldn’t let the whole organization upgrade a real life application yet.
Check out Meron Fridman (@meronfr): https://twitter.com/meronfr?s=09
Check out Lior Arviv (@liorarviv): https://twitter.com/liorarviv?s=09
Check out http://dev.office.com/fabric to get some ready resources.
Using react, Yeoman, node.js
Web parts added from toolbox – Still in development and API changing.
Tool pan became ajax – no need to reload each time to see the change.
The idea is to upload through cloud
Gulp used for build
Yeoman for predefined templates
Can work on Mac also.
The most serious change is the C# to Typescript
Create environment – https://dev.office.com/sharepoint/docs/spfx/set-up-your-development-environment
- yo @microsoft/generator-sharepoint //didn’t work for me yet!!
Answer the questions
- Gulp serve //running the environment
Opens initial work branch
Project structure for web part
In folder src -> webparts -> name of the webpart
Import from “@microsoft/sp-webpart-base”
In render() function adding the html code or template. Better developed with React or Angular 2.
IPropertyPaneSettings defines the properties –> pages and groups inside.
Defining the webpart like assembly info
Predefining the used packages
Need development tenant for sharepoint development
Environmnet.Type == Environment.Local
Enables getting the mockup data on localhost
Otherwise can connect to real data.
Example for online community exmple project – spfx 40 fantastic
https://github.com/Kaidanov/spfx-40-fantastics my fork for Olivers development.
Another tutorial using new SharePoint.
Enjoy the summary and
I would love to hear your insights about new SharePoint release !