Forum Discussion
MicrosoftHave you seen the updates to SharePoint Framework?
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.
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/.
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.
- That's not the message....of course .NET development is still an option, as other development models available today, and you will have scenarios where the new framework does not fit. I recommend you to read Waldek's post about what the new framework means in regards of developing for SharePoint
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
