v16 CSOM assembly seems to miss ComposedLookItemLinkModelHandler

[SubPointSupport]

As per the comments:

"It works with SPMeta2.CSOM.Foundation but not with SPMeta2.CSOM.Foundation-v16
both nuGet packages add an assembly named SPMeta2.CSOM.dll to the project. The SPMeta2.CSOM.Foundation one seems to override the other (-v16)"


var model = SPMeta2Model.NewWebModel(web =>
{
web.AddComposedLookItemLink(new ComposedLookItemLinkDefinition
{
ComposedLookItemName = "..."
});
});
service.DeployWebModel(context, model);

"Value cannot be null.\r\nParameter name: Can't find model handler for type:[SPMeta2.Definitions.ComposedLookItemLinkDefinition]. Current ModelService type: [SPMeta2.CSOM.Standard.Services.StandardCSOMProvisionService]."

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

*.csproj have incorrect build conditions for O365 due to the last v12/v13 build change.

'$(spRuntime)'=='15' Or '$(spRuntime)'=='16' or  '$(Configuration)'=='Debug'

That should include '365' as a spRuntime version as well. The following should be done:

• [DONE] There should be a "baseline stat" file containing the amount of defs and handlers per runtime. The file is to be edited manually, by devs, per release
• [DONE] Build process should also produce a "stat" file and compare with the "baseline"
• [DONE] NuGet packaging should check assemblies as per the "baseline" to ensure the right assemblies are added to the nuGet packages
• [DOME] build should fail if some conditions in the *.csproj files were excluded (handlers aren't there or def aren't there as expected)
• [DONE] NuGet packaging process should check assemblies under lib35/lib40/lib45 and ensure that the libraries are really built with the correct .NET framework version

[SubPointSupport]

*.csproj have incorrect build conditions for O365 due to the last v12/v13 build change.

'$(spRuntime)'=='15' Or '$(spRuntime)'=='16' or  '$(Configuration)'=='Debug'

That should include '365' as a spRuntime version as well. The following should be done:

• There should be a "baseline stat" file containing the amount of defs and handlers per runtime. The file is to be edited manually, by devs, per release
• Build process should also produce a "stat" file and compare with the "baseline"
• NuGet packaging should check assemblies as per the "baseline" to ensure the right assemblies are added to the nuGet packages