Have you seen the updates to SharePoint Framework?

%3CLINGO-SUB%20id%3D%22lingo-sub-1223%22%20slang%3D%22en-US%22%3EHave%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1223%22%20slang%3D%22en-US%22%3E%3CP%3ESliced%20bread%20has%20nothing%20on%20the%20offline-capable%20SharePoint%20Workbench.%20You%20don't%20need%20to%20stand%20up%20a%20dev%2Ftest%20environment%20or%20a%20playground%20online%20tenant.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CDIV%20class%3D%22video-embed-center%20video-embed%22%3E%3CIFRAME%20class%3D%22embedly-embed%22%20src%3D%22https%3A%2F%2Fcdn.embedly.com%2Fwidgets%2Fmedia.html%3Fsrc%3Dhttps%253A%252F%252Fwww.youtube.com%252Fembed%252FT_bGyqKwT4g%253Ffeature%253Doembed%26amp%3Burl%3Dhttp%253A%252F%252Fwww.youtube.com%252Fwatch%253Fv%253DT_bGyqKwT4g%26amp%3Bimage%3Dhttps%253A%252F%252Fi.ytimg.com%252Fvi%252FT_bGyqKwT4g%252Fhqdefault.jpg%26amp%3Bkey%3Db0d40caa4f094c68be7c29880b16f56e%26amp%3Btype%3Dtext%252Fhtml%26amp%3Bschema%3Dyoutube%22%20width%3D%22200%22%20height%3D%22112%22%20scrolling%3D%22no%22%20frameborder%3D%220%22%20allow%3D%22autoplay%3B%20fullscreen%22%20allowfullscreen%3D%22true%22%20title%3D%22Video%22%3E%3C%2FIFRAME%3E%3C%2FDIV%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1223%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-6474%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-6474%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20imagine%20the%20authentication%20side%20of%20that%20getting%20complicated%20but%20I'll%20see%20what%20I%20can%20find.%20Now%20I've%20seen%20the%20new%20framework%20I%20don't%20want%20to%20go%20back%20to%20using%20iframes!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-6446%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-6446%22%20slang%3D%22en-US%22%3EIf%20you%20expose%20your%20SQL%20throught%20a%20REST%20service%2C%20you%20could%20then%20work%20with%20your%20SQL%20Data.%20If%20that%20it's%20not%20possible%2C%20you%20have%20to%20rely%20on%20Provider-Hosted%20Add-ins.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-6438%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-6438%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20liking%20what%20I've%20seen%20so%20far%20but%20I'm%20guessing%20that%20since%20it%20runs%20entirely%20on%20the%20client%20side%20within%20the%20SharePoint%20context%20we%20are%20restricted%20to%20using%20Office%20365%20assets%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20external%20data%20access%20to%20SQL%20is%20needed%20would%20the%20provider%20hosted%20SharePoint%20Add-In%20be%20the%20recommended%20approach%20going%20forward%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-6414%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-6414%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Kunal%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20becuase%20you%20are%20not%20using%20a%20SharePoint%20Online%20Development%20Tenancy%20(Not%20Site%20Collection).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20need%20to%20sign%20up%20for%20a%20development%20tenancy.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENigel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-6386%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-6386%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20a%20very%20exciting%20move.%20I%20have%20downloaded%20tool%20need%20to%20start%20working%20with%20this%20framework.%3C%2FP%3E%3CP%3EBut%20the%20problem%20i%20am%20facing%20now%20is%20when%20i%20browse%20to%20workbench.aspx%20from%20my%20tenant%20it%20gives%20me%20following%20error%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22The%20Requested%20operation%20is%20part%20of%20an%20experiment%20feature%20that%20is%20not%20supported%20in%20the%20current%20environment%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-6170%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-6170%22%20slang%3D%22en-US%22%3E%3CP%3EFYI%2C%20I%20had%20to%20manually%20run%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3Enpm%20install%20--save%20es6-promise%3C%2FPRE%3E%3CP%3Ebefore%20the%20sample%20would%20work.%20Might%20just%20be%20my%20machine%20though.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20are%20the%20project%20files%20supposed%20to%20be%20so%20big.%20The%20hello%20world%20sample%20seems%20to%20download%2097%2C000%20files%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-6139%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-6139%22%20slang%3D%22en-US%22%3E%3CP%3EHey%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20here%20-%26nbsp%3Bthe%20SharePoint%20Framework%26nbsp%3B%3CEM%3Epreview%20%3C%2FEM%3Eis%20released.%3C%2FP%3E%3CP%3ERead%20more%20about%20that%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdev.office.com%2Fblogs%2Fsharepoint-framework-developer-preview-release%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdev.office.com%2Fblogs%2Fsharepoint-framework-developer-preview-release%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGet%20the%20bits%20on%20GitHub%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FSharePoint%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2F%26nbsp%3BZimmergren%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-5142%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-5142%22%20slang%3D%22en-US%22%3E%3CP%3EMost%20Front-End%20developers%20have%20been%20doing%20Front-End%20development%20since%20JavaScript%20was%20called%20LiveScript.%3C%2FP%3E%3CP%3EThey%20have%20been%20doing%20REST%20for%20years.%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20are%20on%20the%20Angular%20band-wagon%20but%20keep%20a%20sharp%20eye%20on%20what%20Rob%20is%20doing%20with%20Aurelia.%3C%2FP%3E%3CP%3EDon't%20expect%20this%20%22FrameWork%22%20or%20%22Workbench%22%20to%20be%20a%20revolution.%3C%2FP%3E%3CP%3EIt%20is%20a%20bunch%20of%20connectors%20to%20connect%20Front-End%20with%20SharePoint%202016%20stuff.%20(And%20oh%20yes%2C%20CSR%2C%20JSLink%20are%20gone)%3C%2FP%3E%3CP%3EAnd%20most%20Fronteers%20will%20probably%20think%20it%20is%20just%20another%20Tell-Sell%20tool%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20500px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F1753i12387A506E8AAA05%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22eggcracker.jpg%22%20title%3D%22eggcracker.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-5088%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-5088%22%20slang%3D%22en-US%22%3EOne%20thing%20to%20keep%20in%20mind.%20It%20is%20looking%20like%20this%20is%20not%20going%20to%20be%20available%20to%20SharePoint%202013.%20I%20know%20of%20at%20least%20one%20attendee%20of%20the%20Dev%20Kitchens%20said%20he%20got%20it%20working%20in%20SP2013%2C%20but%20it%20involved%20some%20hacking%20to%20make%20it%20work.%20You%20really%20don't%20want%20to%20build%20solutions%20on%20a%20jury-rigged%20framework.%3CBR%20%2F%3E%3CBR%20%2F%3EThat%20being%20said%2C%20I%20know%20that%20Eric%20Overfield%20wrote%20a%20blog%20about%20developing%20as%20if%20you%20were%20using%20the%20framework.%20You%20can%20find%20that%20here%3A%20%3CA%20href%3D%22http%3A%2F%2Fwww.sptechcon.com%2Fnews%2Fdont-wait-to-get-started-with-the-sharepoint-framework%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.sptechcon.com%2Fnews%2Fdont-wait-to-get-started-with-the-sharepoint-framework%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20unfortunately%20aren't%20going%20to%20get%20the%20workbench%20which%20is%20a%20significant%20tool%20within%20the%20framework%2C%20but%20you%20can%20at%20least%20develop%20like%20the%20framework%20is%20designed%20to%20be.%3CBR%20%2F%3E%3CBR%20%2F%3EJust%20my%20thoughts%20on%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3648%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3648%22%20slang%3D%22en-US%22%3EInteresting%2C%20YouTube%20is%20blocked%20at%20my%20workplace%2C%20I%20usually%20see%20a%20message%20about%20that%20but%20in%20this%20your%20post%20just%20contains%20whitespace%2C%20no%20hint%20of%20what%20is%20there.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3516%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3516%22%20slang%3D%22en-US%22%3E%3CP%3EI%20pity%20future%20developers%20who%20have%20to%20inherit%20code%20from%20this%20era.%20Too%20many%20options.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3365%22%20slang%3D%22en-US%22%3ERE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3365%22%20slang%3D%22en-US%22%3EEven%20MVPs%20don't%20have%20it.%20Right%20now%20it%20seems%20to%20be%20only%20available%20to%20those%20that%20attended%20the%20SharePoint%20Dev%20Kitchen.%20Personally%2C%20I'm%20not%20too%20worried%20-%20there's%20so%20much%20to%20learn%20already%20from%20Angular%2FReact%2C%20Yeoman%2C%20Gulp%20and%20now%20Webpack.%20Add%20PnP%20JS%20Core%20and%20KurveJS%20and%20there's%20plenty%20of%20stuff%20to%20learn%20right%20now.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3333%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3333%22%20slang%3D%22en-US%22%3EYou%20should!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3162%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3162%22%20slang%3D%22en-US%22%3E%3CP%3EMaybe%20I%20need%20to%20tell%20my%20developer%20to%20learn%20JavaScript.%3Cimg%20id%3D%22smileyhappy%22%20class%3D%22emoticon%20emoticon-smileyhappy%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fi%2Fsmilies%2F16x16_smiley-happy.png%22%20alt%3D%22Smiley%20Happy%22%20title%3D%22Smiley%20Happy%22%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%20Or%20more%20likely%20Typescript%20as%20it%20seems%20much%20less%20horrible%20than%20plain%20JavaScript.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3157%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3157%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EServer%20bad%2C%20client%20good%20has%20been%20the%20message%20from%20Microsoft%20for%20a%20couple%20of%20years%20now.%26nbsp%3B%20OfficeDev%20%2F%20PnP%20has%20a%20good%20series%20of%20videos%20(on%20channel%209%20or%20here%20%3CA%20href%3D%22https%3A%2F%2Fcamo.githubusercontent.com%2F35027fc484857880077408327a701c05d12825cb%2F687474703a2f2f692e696d6775722e636f6d2f4263514576776c2e706e67%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CIMG%20alt%3D%22A%20list%20of%20links%20to%20the%20various%20contact%20points%20for%20the%20Office%20365%20Developer%20Patterns%20and%20Practices%20group%20and%20content.%22%20src%3D%22https%3A%2F%2Fcamo.githubusercontent.com%2F35027fc484857880077408327a701c05d12825cb%2F687474703a2f2f692e696d6775722e636f6d2f4263514576776c2e706e67%22%20border%3D%220%22%20%2F%3E%3C%2FA%3E)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENigel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2817%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2817%22%20slang%3D%22en-US%22%3EBut%20there%20will%20be%20things%20you%20won't%20be%20able%20to%20do%20at%20the%20client%20side...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2699%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2699%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had.%20The%20message%20I%20got%20was%20basically%20Server%20Side%20Bad%2C%20Client%20Side%20Good.%20That's%20fair%20enough%20as%20that%20seems%20to%20be%20the%20way%20of%20things%20and%20has%20been%20for%20some%20time%2C%20I%20just%20worry%20a%20little%20over%20the%20future%20of%20.net%20as%20a%20whole.%20It%20will%20be%20intersting%20to%20see%20how%20.net%20Core%20fares.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2629%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2629%22%20slang%3D%22en-US%22%3EThat's%20not%20the%20message....of%20course%20.NET%20development%20is%20still%20an%20option%2C%20as%20other%20development%20models%20available%20today%2C%20and%20you%20will%20have%20scenarios%20where%20the%20new%20framework%20does%20not%20fit.%20I%20recommend%20you%20to%20read%20Waldek's%20post%20about%20what%20the%20new%20framework%20means%20in%20regards%20of%20developing%20for%20SharePoint%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2597%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2597%22%20slang%3D%22en-US%22%3E%3CP%3EDoes%20this%20mean%20.Net%20is%20no%20longer%20supported%3F%20While%20progress%20marches%20on%20I%20will%20miss%20the%20.Net%20option.%20We%20only%20have%20limited%20developer%20resource%20and%20for%20us%20we've%20been%20able%20to%20use%20essentially%20the%20same%20original%20codebase%20for%20standalone%20asp.net%20sites%2C%20SharePoint%20application%20pages%2C%20examples%20of%20SharePoint%20add-ins%20and%20more%20recently%20Azure%20AD%20apps%20over%20several%20years.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2213%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2213%22%20slang%3D%22en-US%22%3E%3CP%3EAnother%20approach%20that%20you%20could%20choose%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F452%22%20target%3D%22_blank%22%3E%40Robert%20Woods%3C%2FA%3E%26nbsp%3Bwould%20be%20to%20proceed%20with%20your%20project%20but%20postpone%20branding%20discussion%20until%20later%20and%20avoid%20using%20Custom%20Actions%20or%20other%20things%20that%20are%20currently%20blocking%20the%20modern%20UX.%20While%20these%20things%20will%20get%20clarified%20eventually%20it's%20hard%20to%20tell%20when%20exactly%20and%26nbsp%3Bdelaying%20the%20implementation%20of%20the%20uncertain%20pieces%20could%20prevent%20you%20from%20spending%20time%20and%20effort%20no%20something%20that%20would%20block%20you%20later%20on.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2091%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2091%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F452%22%20target%3D%22_blank%22%3E%40Robert%20Woods%3C%2FA%3E%26nbsp%3BIf%20I%20were%20you%2C%20I%20would%20hold%20off%20the%20project%20at%20least%20until%20Microsoft%20Ignite%20where%20we%20should%20have%20a%20more%20clear%20picture%20about%20when%20the%20new%20stuff%20is%20going%20to%20be%20released...and%20when%20I%20say%20new%20stuff%20I'm%20not%20only%20referring%20to%20the%20new%20Framework%20but%20also%20to%20the%20new%20Team%20Sites%2C%20the%20new%20pages%2C%20etc.%20As%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F121%22%20target%3D%22_blank%22%3E%40Waldek%20Mastykarz%3C%2FA%3E%26nbsp%3Bhas%20said%20the%20new%20Framework%20is%20supposed%20to%20be%20released%20at%20some%20time%20in%20the%20summer...indeed%2C%20you%20should%20have%20a%20message%20in%20Office%20365%20message%20center%20saying%20just%20this%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2022%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2022%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20been%20announced%20to%20start%20releasing%20to%20First%20Release%20tenants%26nbsp%3Bthird%20quarter%20this%20year.%20More%20info%20%40%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.office.com%2F2016%2F05%2F04%2Fthe-sharepoint-framework-an-open-and-connected-platform%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.office.com%2F2016%2F05%2F04%2Fthe-sharepoint-framework-an-open-and-connected-platform%2F%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2017%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2017%22%20slang%3D%22en-US%22%3EWhen%20Juan!%20I%20am%20right%20in%20the%20middle%20of%20developing%20an%20intranet%20on%20the%20old%20model%20and%20would%20love%20to%20get%20my%20hands%20on%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2008%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2008%22%20slang%3D%22en-US%22%3EIt's%20coming%20for%20the%20rest%20of%20MVPs%20and%20the%20general%20public%20%3B)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1746%22%20slang%3D%22en-US%22%3ERE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1746%22%20slang%3D%22en-US%22%3EThe%20question%20is%20when%20will%20it%20be%20out%20for%20non-MVPs%20%3F%20-%20We%20have%20not%20got%20to%0Await%20until%20Ignite%20for%20it%20have%20we%20%3F%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1612%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1612%22%20slang%3D%22en-US%22%3EMy%20development%20team%20is%20avid%20for%20the%20new%20SharePoint%20Framework!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1597%22%20slang%3D%22en-US%22%3ERE%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1597%22%20slang%3D%22en-US%22%3ECan't%20wait%20to%20start%20using%20it%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1554%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1554%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20is%20a%20one%20of%20the%20tool%20all%20developers%20were%20awaited..!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1383%22%20slang%3D%22en-US%22%3ERe%3A%20Have%20you%20seen%20the%20updates%20to%20SharePoint%20Framework%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1383%22%20slang%3D%22en-US%22%3EReally%20looking%20forward%20to%20the%20workbench%20preview!%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E
Highlighted
Microsoft

Sliced bread has nothing on the offline-capable SharePoint Workbench. You don't need to stand up a dev/test environment or a playground online tenant.

 

 

29 Replies
Highlighted
Interesting, YouTube is blocked at my workplace, I usually see a message about that but in this your post just contains whitespace, no hint of what is there.
Highlighted
One thing to keep in mind. It is looking like this is not going to be available to SharePoint 2013. I know of at least one attendee of the Dev Kitchens said he got it working in SP2013, but it involved some hacking to make it work. You really don't want to build solutions on a jury-rigged framework.

That being said, I know that Eric Overfield wrote a blog about developing as if you were using the framework. You can find that here: http://www.sptechcon.com/news/dont-wait-to-get-started-with-the-sharepoint-framework

You unfortunately aren't going to get the workbench which is a significant tool within the framework, but you can at least develop like the framework is designed to be.

Just my thoughts on this.
Highlighted

Most Front-End developers have been doing Front-End development since JavaScript was called LiveScript.

They have been doing REST for years. 

They are on the Angular band-wagon but keep a sharp eye on what Rob is doing with Aurelia.

Don't expect this "FrameWork" or "Workbench" to be a revolution.

It is a bunch of connectors to connect Front-End with SharePoint 2016 stuff. (And oh yes, CSR, JSLink are gone)

And most Fronteers will probably think it is just another Tell-Sell tool

 

eggcracker.jpg

 

Highlighted

Hey,

 

It's here - the SharePoint Framework preview is released.

Read more about that here: https://dev.office.com/blogs/sharepoint-framework-developer-preview-release

 

Get the bits on GitHub: https://github.com/SharePoint/

 

/ Zimmergren

Highlighted

FYI, I had to manually run

 

npm install --save es6-promise

before the sample would work. Might just be my machine though.

 

Also, are the project files supposed to be so big. The hello world sample seems to download 97,000 files?

Highlighted

This is a very exciting move. I have downloaded tool need to start working with this framework.

But the problem i am facing now is when i browse to workbench.aspx from my tenant it gives me following error

 

"The Requested operation is part of an experiment feature that is not supported in the current environment"

Highlighted

Hi Kunal

 

This is becuase you are not using a SharePoint Online Development Tenancy (Not Site Collection).

 

You need to sign up for a development tenancy.

 

Regards

 

Nigel

Highlighted

I'm liking what I've seen so far but I'm guessing that since it runs entirely on the client side within the SharePoint context we are restricted to using Office 365 assets?

 

If external data access to SQL is needed would the provider hosted SharePoint Add-In be the recommended approach going forward?

Highlighted
If you expose your SQL throught a REST service, you could then work with your SQL Data. If that it's not possible, you have to rely on Provider-Hosted Add-ins.
Highlighted

I can imagine the authentication side of that getting complicated but I'll see what I can find. Now I've seen the new framework I don't want to go back to using iframes!