All definitions should have a proper VS snippet starting from M2. Just type "m2" in the Visual Studio and have fun.

• [DONE] Webs
• [DONE] Fields
• [DONE] Content types
• [DONE] Lists
• [DONE] List Views
• [DONE] User custom action
• [DONE] Site features
• [DONE] Web features
• [DONE] Sandbox solutions
• [DONE] Security groups
• [DONE] Security roles
• [DONE] Wiki pages
• [DONE] Publishing pages
• [DONE] Web part pages
• [DONE] Quick navigation
• [DONE] Top navigation
• [DONE] Taxonomy store
• [DONE] Tax term set
• [DONE] Tax term
• [DONE] Tax group
• [DONE] Web navigation settings

• implement separate project
• implement *.wsp import provider
• implement T4 templates for code generation
• implement VS project and item templates
• craft NuGet package

Moved from SubPointSolutions/spmeta2#96

Would be nice to have advanced debugger visualization for SPMeta2 models.

'Intranet Model' project is a good starting point, but it takes time for experienced people to delete / comment / remove stuff. There should be an 'Intranet Empty Model' project template as well.

• custom syntax
• custom definition
• custom model handler
• custom logging

• ModelNodeExtensions - mode node extensions
• ModelNodeSyntaxExtensions - syntax extensions

Due to Output/Snippets folders aren't being copied with new Cakebuild #40, there should be additional Pester check on resulting VSIX package. The following check is to be implemented and integrated with CI:

• Unpack VSIX package
• Check Output / Resources / Snippets folders presence
• Check Output -> Item Templates has 3 zip files
• Check Output -> ProjectTemplates has 2 zip files
• Check Snippets -> has *.snippet files
• Check Resources -> has 2 files

That would be great start to gate VSIX related regression.

Template should allow to create a pure c# model without any SharePoint CSOM/SSOM dependency.
That should work along with the console provisioner option.

it would be nice to have snippets for new M2 site and web models.

If I create new project from one of the extension templates the extension adds references to the following DLLs:

• Microsoft.SharePoint.Client.dll
• Microsoft.SharePoint.Client.Runtime.dll
• Microsoft.SharePoint.Client.Taxonomy.dll
• Microsoft.SharePoint.Client.Publishing.dll

But all the aforementioned items reference the 16th version of the DLLs.

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

All pre-created definition class should have commented out instances, so that it would be easy to get started - fields, content types, and so on.

Foundation

• Fields - Text
• Fields - Note
• Fields - Date
• Fields - Date and time
• Fields - Number
• Fields - Number with precision
• Fields - Boolean
• Fields - BusinessData
• Fields - Calculated
• Fields - Currency
• Fields - Choice
• Fields - Multi-choice (various options)
• Fields - URL
• Fields - User
• Fields - User / group
• Content types - item content type
• Content types - document content type
• Content types - inheritance
• Webs - blank site
• Webs - team site
• Webs - web hierarhy
• Site features - TBD
• Web features - MDS, Collaboration lists
• Lists - Lists, Docs, Events, Tasks, Tasks with hierarhy
• List Views - Default, CALM query, Calendar view, Gantt, Quick Edit views
• Top navigation - One and two levels
• Quick navigation - One and two levels
• Web parts - XML based provision, typed CEWP, XsltLIstViewWebPart - on various pages
• Welcome pages - custom welcome pages for web and list
• Web part pages - set of custom pages
• Wiki pages - set of custom pages
• Security groups - set of security groups
• Permission levels - set of permission levels
• Sandbox solution provision - sample
• Master page settings - define OOTb pages plus setting up the page
• Master pages - define OOTB pages, plus a few customizations
• User custom action - jQuery at the site level (plus module file provision via style lib)

Standard

• Fields - HTML field
• Fields - Image field
• Fields - Link field
• Fields - Media field
• Fields - Summary field
• Fields - Taxonomy field
• Content types - publishing page
• Content types - document set
• Webs - publishing site
• Webs - document center
• Site features - Publishing infrastructure, Managemd Metadata navigation
• Web features - Publishing infrastructure
• Taxonomy store - default site store
• Taxonomy term group - several groups
• Taxonomy term set - several temsets
• Taxonomy term - several terms
• Publishing pages - Articles and other OOTB pages

Hi.

After projects creation by SPMeta2 template Assembly Name and Default Namespace are not set to the name on project. They always are SPMeta2.VS.CSharp.ProvisionConsole.

Versions: SPMeta2 Extension 1.2.90.25, VS 2015 update 3.

T4 file for an app.config generating strong-typed c# class is essential to have.

The following notation should be used:

• Start with "Should" converts to boolean
• End with "Count" converts to integer

SubPointSolutions/spmeta2#675

There should be project item templates for the most useful artifacts.

• [DONE] Fields
• [DONE] Content types
• Webs
• Lists
• List views
• Top navigation
• Quick navigation
• Web part pages
• Wiki pages
• Publishing pages
• Welcome pages
• Security groups
• Permission levels
• Web parts
• Sandbox solutions
• User custom actions
• Tax store
• Tax groups
• Tax term sets
• Tax terms

M2 model debugger visualizer would be nice to have. Should be added to the template.

It would be nice to generate JS vars including fieds ids, names; content type ids, names and the rest so that JS based development would be much easier. It would allow to avoid "copy-paste" id ids/internal names from c# code and model definition to JS files.

TS

• c# Namespace -> module
• c# Class -> class

JS

• check the TS output, replicate the same
• check the TS output, replicate the same

With new Cakebuild, resulting VSIX package misses Output/Snippets folders. Needs to be investigated and fixed. Current package produced by Cakebuid is broken and unusable.

Extensions fail to create a new project once Visual Studio 2015 Community is used. Needs to be investigated.

The latest version of the Visual Studio extension seems do not work well with Windows Server 2012 R2. I am getting the error while trying to create project from templates. The previous version works good.

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

Debugger visualizer should have the following layout:

• A tree view on the left
• A property grid on the right

Once a tree node is selected, the full set of the properties should be shown in the property grid on the left.

SPMeta2 1.2.120 should be used

Once created, all projects have to have readme file on how to get started.

Project template should allow to pre-create a console provisioner, so that a project can be deployed with one F5 hit.

Current extensions need to be tested with VS2017

Implicit style library folder should be pre-provisioned with the following items:

• Prj prefix folder name

frameworks / libraries

• jQuery
• jQuery UI
• Angular
• Ember
• KO
• SPServicers
• caml.js
• Backbone
• moment js
• bootstrap

• Recent CakeBuildTools
• Release notes

While project is created with SP2013 CSOM, it must reference v15 assemblies.
Event if v16 exists locally, v15 has to be added.

Delivery via chocolatey gallery is something we need to look into.

• Install-ChocolateyVsixPackage - Downloads and installs a VSIX package for Visual Studio
  https://chocolatey.org/docs/helpers-install-chocolatey-vsix-package

Extensions should be documented as well as landing page needs to be presentable.

Moved from SubPointSolutions/spmeta2#163

M2 should have a better Visual Studio integration to reduce time waste on bootstrapping projects.

Must have features:

• project templates
• item templates

Would be nice to have features:

• console trace integration ??
• T4 templates ??
• Adding T4/PS templates for JS vars generation ??
• Adding SPMeta2 model debugger visualizer ??

Links:

• https://github.com/ligershark/side-waffle/wiki/How-to-create-a-project-template
• http://blogs.endjin.com/2014/07/a-step-by-step-guide-to-developing-visual-studio-item-templates-using-sidewaffle/

As Add M2XXX snippets #8, there should be snippets for the typed web parts as well.

• [TODO] ClientWebPartDefinition
• [TODO] ContentEditorWebPartDefinition
• [TODO] ListViewWebPartDefinition
• [TODO] PageViewerWebPartDefinition
• [TODO] ScriptEditorWebPartDefinition
• [TODO] ClientWebPartDefinition
• [TODO] SilverlightWebPartDefinition
• [TODO] UserCodeWebPartDefinition.
• [TODO] XsltListViewWebPartDefinition
• [TODO] ClientWebPartDefinition
• [TODO] ClientWebPartDefinition

• [TODO] ContactFieldControlDefinition
• [TODO] ContentByQueryWebPartDefinition
• [TODO] ContentBySearchWebPartDefinition
• [TODO] ProjectSummaryWebPartDefinition
• [TODO] RefinementScriptWebPartDefinition
• [TODO] ResultScriptWebPartDefinition
• [TODO] SiteFeedWebPartDefinition
• [TODO] SummaryLinkWebPartDefinition
  .

Project template should ask for a default field / content type metadata group, then generate const class.

It would be nice to have item templates for the following items:

• SiteModel
• RootWebModel
• WebModel