Skip to content

SPMeta2 v1.2.1
Compare
Choose a tag to compare
@SubPointSupport SubPointSupport released this 24 Aug 13:50
· 648 commits to master since this release
1.2.1
8fe0426

SPMeta2 v1.2.1 - August 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 network or sent a ticket here at github:

What's new in v1.2.1

Current assembly file version: 1.2.15236.1334

New definitions

  • No new definition were added

Fixes

  • AddTaxonomyTermLabel() is added under TaxonomyTermDefinition
  • AddSecurityRoleLink() is added on SecurityGroupDefinition
  • Correct XML validation on XML based properties
  • Site provision fixes for SSOM
  • ClientWebPart provision on wiki pages (was failing on ID prop presence)
  • Correct order for content type related operations in the list
  • Correct order for app provision on the web

Enhancements

  • AssemblyFileVersion is updated during the build
  • TaxonomyTermDefinition has CustomProperties property to address custom prop provision
  • SiteDefinition enhanced with required attributes
  • M2 handles starting '/' in the web urls avoiding fails
  • SecurityGroupDefinition allows nesting security groups (for on-prem AD groups and global O365 groups)
  • PublishingPageLayoutDefinition.Title is not required any more, mimic SharePoint
  • ListDefinition.DocumentTemplateUrl is introduced
  • ListViewDefinition has new props - Type/ViewData to support Gantt, Calendar and Datasheet view provision
  • ClientWebPart.ProductWebId is nullable and not required. Current web id will be used if empty
  • WebDefinition supports custom web templates via CustomWebTemplate props
  • TaxonomyFieldDefinition has IsSiteCollectionGroup and GroupName/GroupId props to enhance provision
  • BuiltInSiteFeatures.EnableAppSideLoading props is introduced
  • BuiltInWikiPages and BuiltInPublishingPages classes are introduced\
  • AppDefinition provision supports updates, automatically detect if any is needed
  • ModuleFileUtils.LoadModuleFilesFromLocalFolder() has overload with 'shouldInclude' callback
  • LookupFieldDefinition.RelationshipDeleteBehavior is introduced
  • PublishingPageLayoutDefinition.PreviewImage is introduced
  • Syntax.Extended is added, more details here - #582
  • LookupFieldDefinition.LookupWebUrl is added, ~site and ~sitecolleciton token support is implemented
  • DeleteWebPartDefinition supports DeleteWebPartDefinition.WebParts props and 'Title' match

Regression tests

  • Better web part provision tests - all web parts are deployed to wiki, web part, publishing, list view, new, edit and view list forms
  • New tests on apps / client web part provision on web and subwebs
  • New tests on app upgrades provision
  • New tests on CSOMTokenReplacementService / SSOMTokenReplacementService

Improved and hardened regression tests coverage - 580 tests run again the following three 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 network or sent a ticket here at github:

Assets 2
Loading