07-15-2016 10:59 AM
07-17-2016 08:35 AM
07-18-2016 07:48 AM
07-18-2016 08:14 AM
It's been announced to start releasing to First Release tenants third quarter this year. More info @ https://blogs.office.com/2016/05/04/the-sharepoint-framework-an-open-and-connected-platform/.
07-18-2016 10:45 AM
@Robert Woods If I were you, I would hold off the project at least until Microsoft Ignite where we should have a more clear picture about when the new stuff is going to be released...and when I say new stuff I'm not only referring to the new Framework but also to the new Team Sites, the new pages, etc. As @Waldek Mastykarz has said the new Framework is supposed to be released at some time in the summer...indeed, you should have a message in Office 365 message center saying just this
07-18-2016 10:37 PM
Another approach that you could choose @Robert Woods would be to proceed with your project but postpone branding discussion until later and avoid using Custom Actions or other things that are currently blocking the modern UX. While these things will get clarified eventually it's hard to tell when exactly and delaying the implementation of the uncertain pieces could prevent you from spending time and effort no something that would block you later on.
07-20-2016 04:54 PM
Does this mean .Net is no longer supported? While progress marches on I will miss the .Net option. We only have limited developer resource and for us we've been able to use essentially the same original codebase for standalone asp.net sites, SharePoint application pages, examples of SharePoint add-ins and more recently Azure AD apps over several years.
07-20-2016 11:06 PM
07-21-2016 05:16 AM
I had. The message I got was basically Server Side Bad, Client Side Good. That's fair enough as that seems to be the way of things and has been for some time, I just worry a little over the future of .net as a whole. It will be intersting to see how .net Core fares.
07-21-2016 10:56 AM
07-24-2016 10:41 AM - edited 07-25-2016 08:11 AM
07-25-2016 11:08 PM
07-28-2016 02:34 AM
08-10-2016 07:53 AM
08-10-2016 12:44 PM - edited 08-10-2016 12:50 PM
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
08-17-2016 12:52 PM
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/
08-17-2016 04:07 PM
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?
08-18-2016 10:38 PM
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"
08-19-2016 12:55 AM
This is becuase you are not using a SharePoint Online Development Tenancy (Not Site Collection).
You need to sign up for a development tenancy.
08-19-2016 01:54 AM
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?
08-19-2016 02:10 AM
08-19-2016 05:02 AM
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!