Forum Discussion
Have you seen the updates to SharePoint Framework?
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.
- Michael PerryJul 21, 2016Iron Contributor
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.
- Nigel_Price9911Jul 24, 2016Iron Contributor
Hi
Server bad, client good has been the message from Microsoft for a couple of years now. OfficeDev / PnP has a good series of videos (on channel 9 or here https://camo.githubusercontent.com/35027fc484857880077408327a701c05d12825cb/687474703a2f2f692e696d6775722e636f6d2f4263514576776c2e706e67)
Regards
Nigel
- Michael PerryJul 24, 2016Iron Contributor
Maybe I need to tell my developer to learn JavaScript.:smileyhappy:
Edit: Or more likely Typescript as it seems much less horrible than plain JavaScript.
- Jul 21, 2016But there will be things you won't be able to do at the client side...