Support .NET Core with CSOM
Support .NET Core with CSOM
Shaun Becker
shared this idea
We are still actively working on the needed changes for providing the CSOM API NuGet package also as a .NET Standard version. This is currently planned to happen on the first half of 2020 calendar year. We do apologize the inconvenience caused by the delays on getting this out and acknowledge the massive demand of this capability.
117 comments
-
JM
commented
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 listsRegarding 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:
https://github.com/SharePoint/PnP-Sites-Core/tree/master/Assemblies/16.1Exactly:
https://github.com/SharePoint/PnP-Sites-Core/blob/master/Assemblies/16.1/SharePointPnP.Client.dllThis is coming from the PnP-Team and is unsupported by Microsoft.
So far this works well.
-
Matt
commented
This is a joke right? WTF? Youve now kicked this 3 months twice. Are you taking the piss?
Do you ever plan on releasing this or in 3 months time are you just going to kick it another 3 months?
If there is massive demand, add more resource
We could move to Graph if it wasnt so half-assed and missing features
-
alexander.pajer commented
Vesa ... forget it ... nobody cares about SharePoint anymore .. you managed to kill it and SPFX is a pure mess ... Have you ever heard of Semver and breaking changes? According to this Semver there should be SPFx Version 6 or 7 ... Ever heard of npm audit fix and vulnerabilities? Where is your solution to that? Vulneralbilities coming up every week and than your spfx project upgrade with 50+ commands that have to be executed manually ... ?
-
Matt
commented
Now into April. Please provide an update
-
Anonymous
commented
please any update as it is end of Q1? or another message that this get delayed again?
-
Anonymous
commented
Today is the last day of the first quarter of 2020...
-
Tyler
commented
Any update on this. We are 4 days out from end of quarter.
-
HarishChandra
commented
Exactly when will the CSOM for .Net Core will be available. Any possible dates?
-
Matt
commented
PeanutNinja - Can you make MS finally release this promised software?
-
PeanutNinja
commented
Need Developer? Just contact me at ashlymaepaul@gmail.com
i can do work CSOM in asp.net core just pm me. -
a
commented
any update when will be released?
-
Alan Ahlberg
commented
This is a really important feature. Even a beta-version would be useful at this point.
-
JM
commented
Hi Vesa,
13 days till launch.
I'm starting a new project and needing this features latter on. Can you confirm if the implementation will be delivered on schedule? -
Andre Moraes
commented
Michel Weber
thanks the url that you provide suited my automation needs with LinqPad 6 Scripts that uses .NET core
very much appreciated -
PH
commented
3 weeks and 2 days remaining. Hope to see first core version atleast then. its ok to release some beta version before that so we can start testing! Really hate that we still have to use old net framework webapi project. cant upgrade without net core support. Losing ALOT of money and man hours as have to support and build old api.
-
Anonymous
commented
This delay is causing us a huge amount of money because we have to rebuild stuff using the expiremental .Net Standard CSOM versions and mentioned below and a lot of the PNP stuff.
All of our newer solutions are .Net Standard and .Net Core only and we will not go back using outdated .Net Framework solutions again.
Get your stuff done Microsoft!
-
Anonymous
commented
Less than a month left...
-
Michel Weber
commented
It's a shame there is not a higher priority on this task. I'm already waiting for so long I really don't expect the SharePoint Team to deliver in Q1. I hope they get it done this year.
There is a workaround for now that our team uses:
Use the experimental .NET Standard CSOM:
There is an *experimental* .NET Standard CSOM version available here:
https://github.com/SharePoint/PnP-Sites-Core/tree/master/Assemblies/16.1Exactly:
https://github.com/SharePoint/PnP-Sites-Core/blob/master/Assemblies/16.1/SharePointPnP.Client.dllThis is coming from the PnP-Team and is unsupported by Microsoft.
So far this works well.
-
Martijn
commented
Hi Team,
is there a possibility to share the Abstractions library so that we can make tests en and implementations in parallel?
Thanks in advance
