Skip to content

SPMeta2 v1.2.2, September 2015
Compare
Choose a tag to compare
@SubPointSupport SubPointSupport released this 22 Sep 22:28
· 625 commits to master since this release
1.2.2
56d75bf

SPMeta2 v1.2.2 - September 2015 - release notes

If you have 1.1.XXX and moving to 1.2.XXX please review the following release notes carefully.

The following information aims to provide an overview on assembly related changes, refactorings, API changes, new features and API to prepare and simplify migration from v1.1.XXX to v1.2.XXX.
https://github.com/SubPointSolutions/spmeta2/releases/tag/1.2.0-beta1

Please review it carefully, consider that depending on your solution and API usage additional effort might be required to get updated to v1.2.XXX. Once updated, make sure your solution can be compiled without errors, then give a few rounds of provision.

In case you have unexpected issues please contact support on SPMeta2 Yammer or YouTrack:

AssemblyFileVersion - 1.2.15265.2146

What's new in v1.2.2

New definitions

  • SupportedUICultureDefinition, should be deployed under web

Fixes

  • AddProperty() method on list nodes
  • Fixed security provision for SSOM on wiki, web part and publishing pages

Enhancements

  • Localization support (TitleResource / DescriptionResource) for web, field, content type, list, list view, navigation nodes and user custom actions
  • Enhance 'ModuleFileDefinition' provision - enable security operations #655
  • Correct BuiltInListDefinitions.CustomUrl props, regression tests
  • Version property validation on AppDefinition

Regression tests

  • Improved regression testing

Improved and hardened regression tests coverage - 600+ tests run against the following environments

  • SP2013 SP1+ SSOM
  • SP2013 SP1+ CSOM
  • O365 tenants

Current test coverage is split into three major categories:

  • Classic unit tests for pure c# based API
  • Random generated definition provision - tests deploy several randomly generated artefacts multiple times, then fetch provisioned SharePoint artefacts, compare properties with original definitions, then randomly update original definition properties and make the second round of the provision, fetch and property comparing
  • Scenario based definition provision - manually written provision to cover various real word provision scenarios. Validation process is the same - deploy several times, check, changes, deploy and check again.

Support & Issue Resolution

In case you have unexpected issues please contact support on SPMeta2 Yammer or YouTrack:

Assets 2
Loading