{"id":3305,"date":"2011-12-27T12:35:29","date_gmt":"2011-12-27T04:35:29","guid":{"rendered":"http:\/\/www.sharepointboost.com\/blog\/?p=3305"},"modified":"2023-07-31T11:40:01","modified_gmt":"2023-07-31T03:40:01","slug":"how-to-create-your-sharepoint-visualstudio-multiple-project-template-the-whole-solution","status":"publish","type":"post","link":"https:\/\/www.boostsolutions.com\/blog\/how-to-create-your-sharepoint-visualstudio-multiple-project-template-the-whole-solution\/","title":{"rendered":"How To Create Your SharePoint VisualStudio Multiple Project Template (The Whole Solution)"},"content":{"rendered":"

Are you wasting your time to create a SharePoint foundation solution architecture?<\/p>\n

Let’s assume you are a software architect, and you have to create the template for a new product. It is a repetitive task and will cost you a lot of time for the following:<\/p>\n

You shall define the layers for your solution, such as Presentation Layer, Domain Layer, Data Access Layer, Service Layer, Infrastructure Layer and so on. In other words, you should create different projects in VisualStudio and build the projects relationships.<\/p>\n

You should keep the same technology, otherwise when an employee is transferred from one product team to another, he will have to study a new technology (eg: one product team using Spring.NET IOC container and the other product team using Castle IOC container. What a bad message! The employee should master two different IOC framework).<\/p>\n

Regarding to coding, you should reference the infrastructure assembly (Eg: IOC, AOP, Unit Test framework and so on), attach the xsd schema for xml configuration file input intellisense, and keep the same technology and code structure for all products.<\/p>\n

What happens today?<\/p>\n

You can create your SharePoint VisualStudio multiple project (the whole solution) template now.<\/p>\n

Using it, when you want to start a new product, you can create your foundation code structure with the template. The whole creation process only takes a few seconds, finally you can put away the repetitive work and do something productive.<\/p>\n

Preview of the Solution Template solution<\/p>\n

The “Solution Template” solution is as follows:<\/p>\n

\"\"<\/a><\/p>\n

There are three projects in the solution.<\/p>\n

    \n
  1. Landpy.SolutionTemplate.TemplateContent is the content of the solution template (it includes the code, xsd, reference assembly, project configuration, SNK files and so on)<\/li>\n
  2. Landpy.SolutionTemplate.VSIX is a Extensibility VSIX project, it will generate vsix file which can be installed as a VisualStudio extensibility. You install the extensiblity, then you can create your own solution as the build-in template.<\/li>\n
  3. Landpy.SolutionTemplate.Wizard is the project to dynamically generate some code such as assembly info or namespace. It is always a WinForm project like a wizard when you create the solution with the template.<\/li>\n<\/ol>\n

    How to use the Solution Template<\/strong><\/p>\n

    \"\"<\/a>
    \n<\/strong><\/p>\n

    Step one: Double click the Landpy.SolutionTemplate.VSIX.vsix file to install the extensibility.<\/p>\n

    \"\"<\/a><\/p>\n

    Step Two: Click the Install button.<\/p>\n

    \"\"<\/a><\/p>\n

    Step Three: The extensibility has been installed, click Close button.<\/p>\n

    Note: You should restart your VisualStudio to load the extensibility.<\/p>\n

    \"\"<\/a><\/p>\n

    Step Four: Open Visual Studio, then click the menu File->New->Project, Select the template which will be installed in the last step.<\/p>\n

    \"\"<\/a><\/p>\n

    \"\"<\/a><\/p>\n

    Step Five: With the wizard create the new solution. Only takes you a few seconds.<\/p>\n

    \"\"<\/a><\/p>\n

    Solution Structure<\/p>\n

    \"\"<\/a><\/p>\n

    Assembly info is based on the wizard input.<\/p>\n

    \"\"<\/a><\/p>\n

    CS file is based on the wizard input.
    \nNote: If you want to uninstall the extensibility, you should open VisualStudio and click the menu Tools->Extension Manager…<\/p>\n

    \"\"<\/a><\/p>\n

    Click the Uninstall button to uninstall the extensibility. <\/strong><\/p>\n

    How to develop the Solution Template?<\/strong><\/p>\n

    \"\"<\/a><\/strong><\/p>\n

    Step One: Create a content project:<\/p>\n

    For multiple project template, you should modify the vstemplate file as follows:<\/p>\n

    <?xmlversion=”1.0″encoding=”utf-8″?><\/p>\n

    <VSTemplateVersion=”2.0.0″Type=”ProjectGroup”<\/p>\n

    xmlns=”http:\/\/schemas.microsoft.com\/developer\/vstemplate\/2005″><\/p>\n

    <TemplateData><\/p>\n

    <Name>Landpy SharePoint Solution Template<\/Name><\/p>\n

    <Description>Landpy SharePoint Solution Template<\/Description><\/p>\n

    <Icon>Landpy.SolutionTemplate.TemplateContent.ico<\/Icon><\/p>\n

    <ProjectType>CSharp<\/ProjectType><\/p>\n

    <ProjectSubType>Eisk<\/ProjectSubType><\/p>\n

    <\/TemplateData><\/p>\n

    <TemplateContent><\/p>\n

    <ProjectCollection><\/p>\n

    <SolutionFolderName=”ProductProjects”><\/p>\n

    <ProjectTemplateLinkProjectName=”SystemInterface”><\/p>\n

    ProjectCollection\\SystemInterfaceLayer\\ProjectTemplate.vstemplate<\/p>\n

    <\/ProjectTemplateLink><\/p>\n

    <ProjectTemplateLinkProjectName=”Core”><\/p>\n

    ProjectCollection\\Core\\ProjectTemplate.vstemplate<\/p>\n

    <\/ProjectTemplateLink><\/p>\n

    <ProjectTemplateLinkProjectName=”DomainLayer”><\/p>\n

    ProjectCollection\\DomainLayer\\ProjectTemplate.vstemplate<\/p>\n

    <\/ProjectTemplateLink><\/p>\n

    <ProjectTemplateLinkProjectName=”TestFramework”><\/p>\n

    ProjectCollection\\TestFramework\\ProjectTemplate.vstemplate<\/p>\n

    <\/ProjectTemplateLink><\/p>\n

    <ProjectTemplateLinkProjectName=”UnitTest”><\/p>\n

    ProjectCollection\\UnitTest\\ProjectTemplate.vstemplate<\/p>\n

    <\/ProjectTemplateLink><\/p>\n

    <\/SolutionFolder><\/p>\n

    <\/ProjectCollection><\/p>\n

    <\/TemplateContent><\/p>\n

    <\/VSTemplate><\/p>\n

    There are several ProjectTemplateLink to link the projects vstemplate file.<\/p>\n

    \"\"<\/a><\/p>\n

    The Core, DomainLayer, PresentationLayer, SystemInterfaceLayer, TestFramework, UnitTest projects are not written by hand. There is a function that can export a single project as a template then you can copy the single template into the Solution Template. The steps are the following:<\/p>\n

    \"\"<\/a><\/p>\n

    \"\"<\/a><\/p>\n

    \"\"<\/a><\/p>\n

    In the zip package, you can get the template content.
    \nNote: the cs file Build Action should be “None”.<\/p>\n

    You can get the vstemplate file element info from http:\/\/msdn.microsoft.com\/en-us\/library\/xwkxbww4.aspx<\/a><\/p>\n

    Step Two: Create wizard project<\/p>\n

    It is a Class Library type project, you should reference the System.Windows.Forms, Add a form.<\/p>\n

    namespace Landpy.SolutionTemplate.Wizard\r\n{\r\npublicpartialclassWizardForm : Form\r\n    {\r\npublicstring ProjectName { get; privateset; }\r\npublicstring ProjectNamespace { get; privateset; }\r\npublicstring BoxName\r\n        {\r\nset { this.LayerBox.Text = String.Format(@\"{0} Layer\", value); }\r\n        }\r\n\r\npublic WizardForm()\r\n        {\r\n            InitializeComponent();\r\n        }\r\n\r\nprivatevoid OK_Click(object sender, EventArgs e)\r\n        {\r\nthis.ProjectName = this.ProjectNameValue.Text.Trim();\r\nthis.ProjectNamespace = this.ProjectNamespaceValue.Text.Trim();\r\nthis.Close();\r\nthis.Dispose();\r\n        }\r\n    }\r\n}<\/pre>\n
    And add the Wizard Class which is inherited from IWizard(Microsoft.VisualStudio.TemplateWizardInterface)<\/p>\n
    namespace Landpy.SolutionTemplate.Wizard.SolutionTemplateWizard\r\n{\r\nclassUnitTestWizard : IWizard\r\n    {\r\npublicvoid BeforeOpeningFile(ProjectItem projectItem)\r\n        {\r\n        }\r\n\r\npublicvoid ProjectFinishedGenerating(Project project)\r\n        {\r\n        }\r\n\r\npublicvoid ProjectItemFinishedGenerating(ProjectItem projectItem)\r\n        {\r\n        }\r\n\r\npublicvoid RunFinished()\r\n        {\r\n        }\r\n\r\npublicvoid RunStarted(object automationObject, Dictionary replacementsDictionary, WizardRunKind runKind, object[] customParams)\r\n        {\r\ntry\r\n            {\r\n                replacementsDictionary.Add(\"$DomainLayerProjectName$\",\r\nCommonReplacementsDictionary.ReplacementsDictionary[\"$DomainLayerProjectName$\"]);\r\n                replacementsDictionary.Add(\"$DomainLayerProjectNamespace$\",\r\nCommonReplacementsDictionary.ReplacementsDictionary[\"$DomainLayerProjectNamespace$\"]);\r\n                replacementsDictionary.Add(\"$SystemInterfaceProjectName$\",\r\nCommonReplacementsDictionary.ReplacementsDictionary[\"$SystemInterfaceProjectName$\"]);\r\n                replacementsDictionary.Add(\"$SystemInterfaceProjectNamespace$\",\r\nCommonReplacementsDictionary.ReplacementsDictionary[\"$SystemInterfaceProjectNamespace$\"]);\r\n            }\r\ncatch (Exception exception)\r\n            {\r\nMessageBox.Show(exception.Message);\r\n            }\r\n        }\r\n\r\npublicbool ShouldAddProjectItem(string filePath)\r\n        {\r\nreturntrue;\r\n        }\r\n    }\r\n}<\/pre>\n
    You should configure the vstemplate file as follows:<\/p>\n
    <VSTemplateVersion=”3.0.0″xmlns=”http:\/\/schemas.microsoft.com\/developer\/vstemplate\/2005″Type=”Project”>
    \n<TemplateData>
    \n<Name>BoostSolutions.DomainLayer<\/Name>
    \n<Description><;No description available>;<\/Description>
    \n<ProjectType>CSharp<\/ProjectType>
    \n<ProjectSubType>
    \n<\/ProjectSubType>
    \n<SortOrder>1000<\/SortOrder>
    \n<CreateNewFolder>true<\/CreateNewFolder>
    \n<DefaultName>BoostSolutions.DomainLayer<\/DefaultName>
    \n<ProvideDefaultName>true<\/ProvideDefaultName>
    \n<LocationField>Enabled<\/LocationField>
    \n<EnableLocationBrowseButton>true<\/EnableLocationBrowseButton>
    \n<Icon><\/Icon>
    \n<\/TemplateData>
    \n<TemplateContent>
    \n<ProjectTargetFileName=”BoostSolutions.DomainLayer.csproj”File=”BoostSolutions.DomainLayer.csproj”ReplaceParameters=”true”>
    \n<FolderName=”DemoModule”TargetFolderName=”DemoModule”>
    \n<ProjectItemReplaceParameters=”true”TargetFileName=”Demo.cs”>Demo.cs<\/ProjectItem>
    \n<\/Folder>
    \n<FolderName=”Properties”TargetFolderName=”Properties”>
    \n<ProjectItemReplaceParameters=”true”TargetFileName=”AssemblyInfo.cs”>AssemblyInfo.cs<\/ProjectItem>
    \n<\/Folder>
    \n<ProjectItemReplaceParameters=”false”TargetFileName=”BoostSolutions.snk”>BoostSolutions.snk<\/ProjectItem>
    \n<\/Project>
    \n<\/TemplateContent>
    \n<WizardExtension>
    \n<Assembly>Landpy.SolutionTemplate.Wizard, Version=1.0.0.0, Culture=neutral, PublicKeyToken=2a7779dfd1034e2f<\/Assembly>
    \n<FullClassName>Landpy.SolutionTemplate.Wizard.SolutionTemplateWizard.DomainLayerWizard<\/FullClassName>
    \n<\/WizardExtension>
    \n<\/VSTemplate><\/div>\n
     <\/p>\n
    WizardExtension element will reference the wizard assembly.<\/p>\n
    namespace Landpy.SolutionTemplate.Wizard.SolutionTemplateWizard\r\n{\r\nclassDomainLayerWizard : IWizard\r\n    {\r\nprivateWizardForm wizardForm;\r\n\r\npublicvoid BeforeOpeningFile(ProjectItem projectItem)\r\n        {\r\n        }\r\n\r\npublicvoid ProjectFinishedGenerating(Project project)\r\n        {\r\n        }\r\n\r\npublicvoid ProjectItemFinishedGenerating(ProjectItem projectItem)\r\n        {\r\n        }\r\n\r\npublicvoid RunFinished()\r\n        {\r\n        }\r\n\r\npublicvoid RunStarted(object automationObject, Dictionary replacementsDictionary, WizardRunKind runKind, object[] customParams)\r\n        {\r\ntry\r\n            {\r\nthis.wizardForm = newWizardForm();\r\nthis.wizardForm.BoxName = \"Domain\";\r\nthis.wizardForm.ShowDialog();\r\n                replacementsDictionary.Add(\"$DomainLayerProjectName$\",\r\nthis.wizardForm.ProjectName);\r\n                replacementsDictionary.Add(\"$DomainLayerProjectNamespace$\",\r\nthis.wizardForm.ProjectNamespace);\r\nCommonReplacementsDictionary.ReplacementsDictionary.Add(\"$DomainLayerProjectName$\",\r\nthis.wizardForm.ProjectName);\r\nCommonReplacementsDictionary.ReplacementsDictionary.Add(\"$DomainLayerProjectNamespace$\",\r\nthis.wizardForm.ProjectNamespace);\r\n                replacementsDictionary.Add(\"$SystemInterfaceProjectName$\",\r\nCommonReplacementsDictionary.ReplacementsDictionary[\"$SystemInterfaceProjectName$\"]);\r\n                replacementsDictionary.Add(\"$SystemInterfaceProjectNamespace$\",\r\nCommonReplacementsDictionary.ReplacementsDictionary[\"$SystemInterfaceProjectNamespace$\"]);\r\n            }\r\ncatch (Exception exception)\r\n            {\r\nMessageBox.Show(exception.Message);\r\n            }\r\n        }\r\n\r\npublicbool ShouldAddProjectItem(string filePath)\r\n        {\r\nreturntrue;\r\n        }\r\n    }\r\n}<\/pre>\n
    The “$DomainLayerProjectName$”<\/span> can be input in wizard form, and will be replaced in the generated file:<\/p>\n
    namespace $DomainLayerProjectName$.DemoModule\r\n{\r\npublicclassDemo : IDemo\r\n    {\r\n        [NotThrowException]\r\n        [LogException]\r\npublicint TestMethod()\r\n        {\r\nreturn 1314;\r\n        }\r\n\r\n        [NotThrowException]\r\n        [LogException]\r\npublicint TestMethodWithException()\r\n        {\r\nthrownew System.NotImplementedException();\r\n        }\r\n    }\r\n}<\/pre>\n
    \"\"<\/a><\/p>\n
    Step Four: Create a VSIX Project<\/p>\n
    \"\"<\/a><\/p>\n
    \"\"<\/a><\/p>\n
    Add the Wizard and Template Content project into the VSIX Project.<\/p>\n
    Note: the Product name and author should not be too long, or when we install the extensibility a System.IO.PathTooLongException exception will occur.<\/p>\n
    Build the VSIX project, and now you have your own Solution Template.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Are you wasting your time to create a SharePoint foundation solution architecture? Let’s assume you are a software architect, and you have to create the template for a new product. It is a repetitive task and will cost you a lot of time for the following: You shall define the layers for your solution, such […]<\/p>\n","protected":false},"author":26,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[125],"tags":[298],"_links":{"self":[{"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/3305"}],"collection":[{"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=3305"}],"version-history":[{"count":6,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/3305\/revisions"}],"predecessor-version":[{"id":9258,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/3305\/revisions\/9258"}],"wp:attachment":[{"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=3305"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=3305"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.boostsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=3305"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}