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

Add detection of CSOM/SSOM support of the target model #750

Closed
SubPointSupport opened this issue Dec 20, 2015 · 2 comments
Closed

Add detection of CSOM/SSOM support of the target model #750

SubPointSupport opened this issue Dec 20, 2015 · 2 comments

Comments

@SubPointSupport
Copy link
Contributor

Model can have some definitions unsupported by CSOM. There should be a way to detect these defs and nodes.

That would enable validation on CSOM/O365 compatibility as well as better 3rd part tooling support.

@SubPointSupport SubPointSupport self-assigned this Dec 20, 2015
@SubPointSupport SubPointSupport changed the title Add detection of csom and ssom support of the model Add detection of CSOM/SSOM support of the target model Dec 20, 2015
@SubPointSupport SubPointSupport modified the milestones: 2016.01.25, 2016.02.08 Feb 6, 2016
@andreasblueher
Copy link
Contributor

Do you have any idea on how this could be implemented? As discussed in yammer I like the idea and would like to have something like that for M2

@SubPointSupport
Copy link
Contributor Author

The folllwing test were added:

  • Should_Pass_On_Valid_SSOM_CSOM
  • Should_Pass_On_Valid_SSOM_Invalid_CSOM
  • Should_Pass_On_Valid_SSOM_Invalid_CSOM_2

The following API was added:

  • SPMeta2Model.IsCSOMCompatible(model)
  • SPMeta2Model.IsSSOMCompatible(model)
  • SPMeta2Model.CheckProvisionCompatibility(model)

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

2 participants