Support .NET Core with CSOM
Support .NET Core with CSOM
Thanks for your feedback! We’re happy to report that your suggestion is now part of the newly released SharePoint Online CSOM API NuGet package.
See more details from following blog post where we reference additional documentation on the usage and have also a video on showing this in practice – https://developer.microsoft.com/en-us/microsoft-365/blogs/net-standard-version-of-sharepoint-online-csom-apis
135 commentsComments are closed
If you do not support credentials and therefore basically "just" the AddIn-Model Authentication, please at least fix it that way, so that we are able to do all the stuff with that.
Especially AppOnly-Authentication does not allow to access the UserProfile Service or the Taxonomy-Service. We have to use Credentials for that currently.
So at least give us the possibility to do automated Tasks like updating some user profile-settings or syncing something into the Taxonomy-Tree.
Vasanth TT commented
We also interested in beta testing. Please prerelease package in nuget thanks
Maybe it's time to go https://go.spflow.com/
I wish the new Microsoft SharePoint leadership would reconsider your approach to SharePoint on-premise environments.
As of late, the general attitude the new team has taken to the SharePoint on-premise Community has been "come on guys, catch up to modern times". However, you're forgetting that the greatest challenge to moving online is data governance. A lot of companies are just not set up to tackle it properly. With an on-premise SharePoint install, companies can at least solve a lot of their governance concerns by just restricting direct external access to their SharePoint farm. After all, how many corporations do you know that actually allow staff direct access over the internet to their corporate document management system?
I wish the new leadership would stop treating SharePoint 2019 like it's competing with Wordpress; and remember to a lot of people, SharePoint was a document management system with Wordpress-like features. Continuously implementing and advertising new features in SharePoint Online with no plans also introduce those features to SharePoint on-premise isn't going to entice people to move to SharePoint Online. Instead, it builds resentment and makes big companies revisit the idea of moving to other document management platforms. And before you turn your nose, remember a lot of us made our livings and businesses around those 200-staff/1000-staff companies with on-premise SharePoint installations. It's a hell of a thing to tell us Partners "well, tough [you know what]".
Willem-Jan Groenestein commented
I would like to get some clarification on the OnPremises statement. Currently we use the a recent version of the CSOM Nuget package to target SP 2013, 2016, 2019 and Online (we have featureflags/checks in place based on the ServerLibraryVersion). We have been waiting for proper .NET Standard implementation which we hope would give us 2 things. 1. A migration path towards .NET Core and 2. a proper async implementation (the last time we checked the async implementation is only partially async and blocks on e.g. FormDigest retrieval). With the given statement for on premises (2013, 2016, 2019) would that mean that we can no longer use our current strategy? If so, what is the proposed way of Microsoft to still supporting all these versions from the same process?
In addition, I see that suddenly "the upcoming .NET Core version" is mentioned though in previous updates it was .NET standard, is this a mistake and will the release still be .NET standard (2.0) so there is a migration path?
Dennis Bradley commented
Sorry, but this is ridiculous. It takes Microsoft 2 years to release CSOM for .NET Core and now it will not even work on premise. Nice to know Microsoft does not really care about developers.
On the on-premises support. As CSOM API has a dependency on the server-side assemblies, which we are not planning to significantly update for the SharePoint 2016 and SharePoint 2019, we cannot unfortunately provide on-premises support with the upcoming release.
This means that the upcoming .NET Core version of CSOM will be only supported in SharePoint Online.
Dennis Bradley commented
Are you saying that you will only support Sharepoint Online on .NET CORE CSOM without supporting on premise in general?
This would be ridiculous.
No public pre-release version for now. We are currently testing this internally and are planning to get it out in few weeks if there's no surprises, but looking good.
Good thing to know that it will NOT support usage of SharePointOnlineCredentials as that does not support MFA. You can use Azure AD app registration etc for the authentication model. So moving away from the legacy auth options to align with future models.
This is also only released for SharePoint Online without support for on-premises.
any prerelease versions for .net core?
Open source it, we will coded it :P
Hello Microsoft. Perhaps you could give an update on this, and whether COVID-19 will mean further delays? We've been waiting very eagerly for an update as we're a DotNet-core-first development shop.
Yes indeed beta or even alpha package is welcome! We can test it and give feedback. I hope if no beta does not mean that the development has not even started yet. (feeling dissy)
we need this so much, can you provide beta package? whatever will work to pogress with this is welcome.
any dates? may or june? we need this as soon as possible.
Gabriel Smoljár commented
This is even more urgent now that ASP.NET Core 3 is not running on .NET Framework.
Alan Ahlberg commented
I have a firm speculation that the fix is coming out when Patrick Rothfuss releases the doors of stone.
Microsoft started "Working On IT" two years ago (12 April 2018).
There are some sites with freelancers that could do this for Microsoft if they don't have the time.
I really don't get why you push everyone to .Net Core, Azure and to Office 365 and don't allow people to use them.
Michel Weber commented
I hate to be right. You will probably not deliver on this too. I expect that if you deliver (which is not very probable) it will be at the end of this year.
It's a bad practice to even use SharePoint in many cases. Only use it if you absolutely must and cannot use any other alternatives.
- Only use SPFx Webparts if you need to run client-side in SharePoint without any outside dependencies (if you need a WebAPI running custom (elevated) code - implement the GUI there).
- Use Azure Blob Storage instead of SharePoint Document Libraries
- Use SQL Server instead of lists
Regarding the CSOM API NuGet package .NET Standard version:
There is a workaround that our team uses:
Use the experimental .NET Standard CSOM:
There is an *experimental* .NET Standard CSOM version available here:
This is coming from the PnP-Team and is unsupported by Microsoft.
So far this works well.