Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix breaking changes caused by recent Microsoft.SharePointOnline.CSOM package #878

Closed
SubPointSupport opened this issue Aug 30, 2016 · 1 comment

Comments

@SubPointSupport
Copy link
Contributor

The latest SharePoint Online CSOM packages seem to have build version BELOW the oldest package available. That caused breaking change while updating CSOM runtime with SPMeta2 to the latest and greatest.

More details can be found in Yammer, the issue needs to be fixed from our side as it does not seem new CSOM packages would follow recommended NuGet versioning strategy.

https://www.yammer.com/spmeta2feedback/#/Threads/show?threadId=688782726

@SubPointSupport SubPointSupport self-assigned this Aug 30, 2016
@SubPointSupport SubPointSupport modified the milestone: 1.2.90 release Aug 30, 2016
@SubPointSupport SubPointSupport modified the milestones: 1.2.90 release, 2016.10.03, 1.2.90 Sep 27, 2016
SubPointSupport added a commit that referenced this issue Oct 3, 2016
…OM package #878

+ added O365 - 16.1.5715.1200 assemblies
+ added NuGet ref to Microsoft.SharePointOnline.CSOM 16.1.5715.1200 for O365 build
@SubPointSupport
Copy link
Contributor Author

  • Moved O365 runtime to O365 - 16.1.5715.1200 for O365 M2 package
  • Added NuGet ref to Microsoft.SharePointOnline.CSOM 16.1.5715.1200 for O365 M2 package

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant