SubPointSupport

Updating with some roadmap. Key focus in to get Docker image built with @colindekker branch https://github.com/colindekker/spmeta2 Once done, we'll focus on CI, most likely Travis CI for Docker based built....

Successfully build @colindekker branch with the default microsoft/dotnet container: **Dockerfile** ```Dockerfile FROM microsoft/dotnet ```` **Then build** ```bash git clone https://github.com/colindekker/spmeta2.git cd spmeta2 dotnet build ``` **Output** https://gist.github.com/SubPointSupport/4ea41e6da81b8bfef750edf2308feee0 These are super-awesome...

Until we get a great solution and nice looking API around this one, there are a few kind of dirty workarounds: ```cs /// use this static list, clean up ModelWeigh...

Not at the moment, renaming content type within a list isn't supported yet. First of all, can't see this feature being popular or demanded. Secondly, it would be a bit...

Maybe, at ContentTypeLinkDefinition, we might enable Name property update if only resolution worked well by ID. Would it be sufficient, @HeToC ? But again, could be a potential way to...

That's a nice feature we would like to support and implement. Lookup provision is a bit of a challenge and needs to be simplified. As you guys suggested, with some...

No, will be postponed for a week or so. Still on the roadmap.

Related to Enhance document set API #453

Here is what can be done to work around it. This is fast-get-it-done workaround without any elegance. Right now SPMeta2 does not support custom fields unless plain FieldDefinition is used...

@digital88, could you please describe the issue? We'd like to understand what exactly is wrong with the provisioning order for security groups and roles. It might be a separate issue...