SharePoint Dev Platform

← SharePoint Experiences in Office365 and/or SharePoint Server

We have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

I suggest you ....

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

When an admin closes an idea you've voted on, you'll get your votes back from that idea.
You can remove your votes from an open idea you support.
To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".

Enter your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

Support .NET Core with CSOM

Support .NET Core with CSOM
654 votes
Vote

Sign in
prestine

Your name

Your email address
Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

You have left! (?) (thinking…)
14 comments · SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Delete… · Admin →

working on it · AdminSharePoint Dev Platform Team (Admin, Microsoft SharePoint) responded

Thanks for your feedback! Just a note to let you know that we’re building your suggestion now. Just to be precise, we are looking into having a .NET Standard version of the CSOM package, so that it’s usable in both older .NET versions and also in the .NET Core. No ETA at this point, but happy to inform that work is in progress.
Add support for library packages in the SharePoint Framework

When building web parts I'd like to be able to extract common code to a separate library that can be shared amongst the different web parts.

Related issue on GitHub: https://github.com/SharePoint/sp-dev-docs/issues/467#issuecomment-284631927
373 votes
Vote

Sign in
prestine

Your name

Your email address
Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

You have left! (?) (thinking…)
9 comments · SharePoint Framework · Flag idea as inappropriate… · Delete… · Admin →

working on it · AdminSharePoint Dev Platform Team (Admin, Microsoft SharePoint) responded

Thanks for your feedback! Just a note to let you know that this is absolutely in our roadmap and we are planning to address this request in future. Good to have though also the vote counts, so that we understand the demand around the request, which helps on prioritizing our internal work.
REST API citizenship! (surface, roadmap and change log)

Besides the lack of detailed documentation around the REST API, given its importance as a major entry point for apps, it needs to be treated with more respect as a service offering. It's currently being updated in CUs and on SharePoint online without any notification of the changes being made (such as the $metadata endpoint appearing - was it in the August 2013 CU for on-prem?). We either need it to be released in a non-breaking change model (URL versioning such as the Twilio model), or messaging needs to be improved so we know when things are going to be changed. Having a log of changes that have been made to date would be helpful, along with understanding what changes are currently in the queue. For example, I would LOVE to know if the end game for the _api endpoint is to finally be a first-class OData v3 endpoint sometime soon.
Besides the lack of detailed documentation around the REST API, given its importance as a major entry point for apps, it needs to be treated with more respect as a service offering. It's currently being updated in CUs and on SharePoint online without any notification of the changes being made (such as the $metadata endpoint appearing - was it in the August 2013 CU for on-prem?). We either need it to be released in a non-breaking change model (URL versioning such as the Twilio model), or messaging needs to be improved so we know when things are going to be…
228 votes
Vote

Sign in
prestine

Your name

Your email address
Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

You have left! (?) (thinking…)
0 comments · SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Delete… · Admin →

working on it · AdminSharePoint Dev Platform Team (Admin, Microsoft SharePoint) responded

Thank you for your input. REST APIs are absolutely critical for the SharePoint Framework and for other customizations. We are working on improving the existing documentation and to ensure that you can more efficiently take advantage of the SharePoint REST APIs in your development.

Don't see your idea?

SharePoint Dev Platform

I suggest you ....

There are two ways to get more votes:

Support .NET Core with CSOM

Add support for library packages in the SharePoint Framework

REST API citizenship! (surface, roadmap and change log)

Feedback

SharePoint Dev Platform

Feedback and Knowledge Base

Searching…

Give feedback

Microsoft SharePoint

Your password has been reset