SPSF SharePoint Software Factory

Commented Unassigned: Problem installing SPSF into Visual Studio 2010 Premium [7453]

matein78 — Wed, 22 May 2013 12:11:12 GMT

When trying to install SPSF (latest version) into VS2010 Premium the installer says that "The Extention manifest is invalid" if i google te problem then the manifest should be changed...
Comments: ** Comment from web user: matein78 **

Sorry, don't get your point here.

The versions as stated in the matrix are still the supported versions. The column titles are links to the coresponding releases for the different VS versions.
The releases in the download section have the supported version in the title.

If you have a look in the release notes of the VS2012 version you notice that the main difference between the two different versions is, that 4.1 drops VS2008, VS2010 and SP2007 but adds support for VS2012 and SP2013.
Apart from that the feature set is 99% the same.

The VS2008/VS2010 version is therefore still a valid release and just will not be updated with new features in the future, as supporting 3 VS versions and 3 SP versions is just a little too much.

Commented Unassigned: Problem installing SPSF into Visual Studio 2010 Premium [7453]

bclevering — Wed, 22 May 2013 11:21:46 GMT

That's what i figured out... but on the homepage you say that different types of installation are supported:

Supported Configurations

Visual Studio 2012 Visual Studio 2010 Visual Studio 2008 (english)
SharePoint 2013 yes no no
SharePoint 2010 yes yes yes
SharePoint 2007 no yes yes

and later on in the story this is also still the case...

Commented Unassigned: Problem installing SPSF into Visual Studio 2010 Premium [7453]

matein78 — Wed, 22 May 2013 09:28:54 GMT

Do you mean with "latest version" the one for VS2008/VS2010 ([SPSF 3.2](https://spsf.codeplex.com/releases/view/82226))?
That one hasn't been changed a while now and should work fine in VS2010. Further development for this version has been discontinued.

The real "latest version" supports only VS2012 ([SPSF 4.1](https://spsf.codeplex.com/releases/view/103498)).

Created Unassigned: Problem installing SPSF into Visual Studio 2010 Premium [7453]

bclevering — Wed, 22 May 2013 08:28:49 GMT

When trying to install SPSF (latest version) into VS2010 Premium the installer says that "The Extention manifest is invalid" if i google te problem then the manifest should be changed...

Closed Feature: Naming convention FeatureReceiver [6062]

matein78 — Thu, 16 May 2013 11:15:21 GMT

Add "EventReceiver" to default name of feature receiver

Commented Issue: Exception when trying to add Custom Form to ContentType [7433]

matein78 — Mon, 13 May 2013 13:59:47 GMT

We get the following exception when we try to execute the ContentTypeCustomForm.xml recipe:

Microsoft.Practices.RecipeFramework.ActionExecutionException: An exception occurred during the binding of reference or execution of recipe ContentTypeCustomForm. Error was: Action AddCustomForms failed to execute:
Exception of type 'Microsoft.Practices.RecipeFramework.VisualStudio.Library.Templates.TemplateException' was thrown..
You can remove the reference to this recipe through the Guidance Package Manager. ---> Microsoft.Practices.RecipeFramework.VisualStudio.Library.Templates.TemplateException: Exception of type 'Microsoft.Practices.RecipeFramework.VisualStudio.Library.Templates.TemplateException' was thrown.
at SPALM.SPSF.Library.Actions.BaseItemAction.Render(String templateCode, String templateFile)
at SPALM.SPSF.Library.Actions.BaseItemAction.GenerateContent(String templateFilename, String targetFilename, NameValueCollection overrideArguments)
at SPALM.SPSF.Library.Actions.BaseItemAction.GenerateContent(String templateFilename, String targetFilename)
at SPALM.SPSF.Library.Actions.BaseTemplateAction.Execute()
at SPALM.SPSF.Library.Actions.AddTemplateToItemAction.Execute()
at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionExecutionService.Execute(String actionName, Dictionary\`2 inputValues)
at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionExecutionService.Execute(String actionName)
at SPALM.SPSF.Library.Coordinators.ConditionalCoordinator.Run(Dictionary\`2 declaredActions, XmlElement coordinationData)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
--- End of inner exception stack trace ---
at Microsoft.Practices.RecipeFramework.Recipe.UndoExecutedActionsAndRethrow(Exception ex)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
at Microsoft.Practices.RecipeFramework.Recipe.Execute(Boolean allowSuspend)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(String recipe, IAssetReference reference, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(IAssetReference reference)
at Microsoft.Practices.RecipeFramework.RecipeReference.OnExecute()
at Microsoft.Practices.RecipeFramework.AssetReference.Execute()
at Microsoft.Practices.RecipeFramework.VisualStudio.RecipeMenuCommand.OnExec()
at Microsoft.Practices.RecipeFramework.VisualStudio.AssetMenuCommand.Invoke()

What's wrong? How to debug?
Attached our dump of installed Visual Studio add-ins.
Comments: ** Comment from web user: matein78 **

Sorry, the formatting did go wrong. But you get the picture :)

Commented Issue: Exception when trying to add Custom Form to ContentType [7433]

matein78 — Mon, 13 May 2013 13:58:33 GMT

I found the issue and will fix it in the next release.

As a quick workaround edit the C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\<shortGUID>\Recipes\Artefacts\ListAndDoc\ContentTypeCustomForm.xml file

find
<Argument Name="ContentTypeUniqueName">
<ValueProvider Stage="OnBeforeActions" Type="Evaluator" Expression="$(SafeAppName)_$(ContentTypeSafeName)" />
</Argument>
and add following code afterwards (line 57)

The recipe will work then (after you closed and opened the solution again) but will only add the custom forms for standard list content types (in case you want one for a document content type 0x0101 would be required in the value field)

The final fix will then provide the actual parent content type of the selected content type.

Commented Issue: Exception when trying to add Custom Form to ContentType [7433]

bclevering — Fri, 10 May 2013 07:25:23 GMT

@matein78; your assumption is correct... Only when you create a recipe afterwards the creation of the contenttype this error occurs.

Commented Issue: Exception when trying to add Custom Form to ContentType [7433]

matein78 — Thu, 09 May 2013 21:46:13 GMT

Seems like a bug in the recipe "Add CustomForums to Content Type", which might have been introduces with the upgrade to VS2012.
I will fix it in the next release.

As a workaround, you can create the custom forms along with the content type in the content type recipe instead.

New Post: Error Creating a new Custom Action

matein78 — Thu, 09 May 2013 21:31:09 GMT

This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.

Created Issue: Error Creating a new Custom Action [7436]

matein78 — Thu, 09 May 2013 21:31:05 GMT

I received the following error from the current release (as of 05/08/2013) creating a custom action

Steps:
1) SPSF Artefacts -> Custom Actions and Ribbons -> Custom Action Group

2) Provide Name for CA GROUP -> Press OK

3) New Parent Feature, Used Defaults for Name/Title/Description, Scope = Farm and selected Create Feature Receiver

4) Used Default Title,Description, Ensured Sequence was 100, Set Location to Microsoft.SharePoint.Administration.ApplicationManagement (Microsoft.SharePoint.Administration.ApplicationManagement)

5) Pressed Finish

Error:

Microsoft.Practices.RecipeFramework.ActionExecutionException: An exception occurred during the binding of reference or execution of recipe CustomActionGroup. Error was: Action CreateElementsXml failed to execute:
Feature CTP_FBA_ADLDSConfiguration not found. Could not add feature to package..
You can remove the reference to this recipe through the Guidance Package Manager. ---> System.Exception: Feature CTP_FBA_ADLDSConfiguration not found. Could not add feature to package.
at SPALM.SPSF.Library.Helpers2.AddVSElementToVSFeature(DTE dte, Project project, ProjectItem elementFolder, String evaluatedParentFeatureName)
at SPALM.SPSF.Library.Actions.AddElementsDefinitionAction.AddElementsDefinitionToVSTemplate(DTE dte, Project project, String evaluatedParentFeatureName, String evaluatedSPDataTemplate, String evaluatedElementsTemplate, String evaluatedElementsCategory, String evaluatedElementsName, String evaluatedTargetFileName)
at SPALM.SPSF.Library.Actions.AddElementsDefinitionAction.Execute()
at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionExecutionService.Execute(String actionName, Dictionary`2 inputValues)
at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionExecutionService.Execute(String actionName)
at SPALM.SPSF.Library.Coordinators.ConditionalCoordinator.Run(Dictionary`2 declaredActions, XmlElement coordinationData)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
--- End of inner exception stack trace ---
at Microsoft.Practices.RecipeFramework.Recipe.UndoExecutedActionsAndRethrow(Exception ex)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
at Microsoft.Practices.RecipeFramework.Recipe.Execute(Boolean allowSuspend)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(String recipe, IAssetReference reference, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.GuidancePackage.ExecuteFromTemplate(String recipe, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate.ExecuteRecipe(Boolean executeActions)
at Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate.RunFinished()

New Post: Error Creating a new Custom Action

matein78 — Thu, 09 May 2013 21:30:14 GMT

Thx for reporting the issue and the detailed steps to reproduce.
I will look into it to fix it in the next release.
BTW, don't hesitate to add such issues directly to the issue tracker.

Best Regards

Matthias

Created Issue: Exception when trying to add Custom Form to ContentType [7433]

cveld — Wed, 08 May 2013 15:00:23 GMT

We get the following exception when we try to execute the ContentTypeCustomForm.xml recipe:

Microsoft.Practices.RecipeFramework.ActionExecutionException: An exception occurred during the binding of reference or execution of recipe ContentTypeCustomForm. Error was: Action AddCustomForms failed to execute:
Exception of type 'Microsoft.Practices.RecipeFramework.VisualStudio.Library.Templates.TemplateException' was thrown..
You can remove the reference to this recipe through the Guidance Package Manager. ---> Microsoft.Practices.RecipeFramework.VisualStudio.Library.Templates.TemplateException: Exception of type 'Microsoft.Practices.RecipeFramework.VisualStudio.Library.Templates.TemplateException' was thrown.
at SPALM.SPSF.Library.Actions.BaseItemAction.Render(String templateCode, String templateFile)
at SPALM.SPSF.Library.Actions.BaseItemAction.GenerateContent(String templateFilename, String targetFilename, NameValueCollection overrideArguments)
at SPALM.SPSF.Library.Actions.BaseItemAction.GenerateContent(String templateFilename, String targetFilename)
at SPALM.SPSF.Library.Actions.BaseTemplateAction.Execute()
at SPALM.SPSF.Library.Actions.AddTemplateToItemAction.Execute()
at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionExecutionService.Execute(String actionName, Dictionary`2 inputValues)
at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionExecutionService.Execute(String actionName)
at SPALM.SPSF.Library.Coordinators.ConditionalCoordinator.Run(Dictionary`2 declaredActions, XmlElement coordinationData)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
--- End of inner exception stack trace ---
at Microsoft.Practices.RecipeFramework.Recipe.UndoExecutedActionsAndRethrow(Exception ex)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
at Microsoft.Practices.RecipeFramework.Recipe.Execute(Boolean allowSuspend)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(String recipe, IAssetReference reference, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(IAssetReference reference)
at Microsoft.Practices.RecipeFramework.RecipeReference.OnExecute()
at Microsoft.Practices.RecipeFramework.AssetReference.Execute()
at Microsoft.Practices.RecipeFramework.VisualStudio.RecipeMenuCommand.OnExec()
at Microsoft.Practices.RecipeFramework.VisualStudio.AssetMenuCommand.Invoke()

What's wrong? How to debug?
Attached our dump of installed Visual Studio add-ins.

New Post: Error Creating a new Custom Action

underwmd — Wed, 08 May 2013 13:23:43 GMT

The list of custom actions is also not updated for 2010/2013. It defaults to adding the CA to Microsoft.SharePoint.Administration.ApplicationManagement.

New Post: Error Creating a new Custom Action

underwmd — Wed, 08 May 2013 13:07:43 GMT

2 inputValues)

   at Microsoft.Practices.RecipeFramework.Recipe.Microsoft.Practices.RecipeFramework.Services.IActionExecutionService.Execute(String actionName)

   at SPALM.SPSF.Library.Coordinators.ConditionalCoordinator.Run(Dictionary

2 declaredActions, XmlElement coordinationData)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
--- End of inner exception stack trace ---
at Microsoft.Practices.RecipeFramework.Recipe.UndoExecutedActionsAndRethrow(Exception ex)
at Microsoft.Practices.RecipeFramework.Recipe.ExecuteActions(IDictionaryService readOnlyArguments, IDictionaryService arguments, ITypeResolutionService resolution)
at Microsoft.Practices.RecipeFramework.Recipe.Execute(Boolean allowSuspend)
at Microsoft.Practices.RecipeFramework.GuidancePackage.Execute(String recipe, IAssetReference reference, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.GuidancePackage.ExecuteFromTemplate(String recipe, IDictionary arguments)
at Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate.ExecuteRecipe(Boolean executeActions)
at Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate.RunFinished()

Updated Wiki: Home

matein78 — Mon, 29 Apr 2013 18:09:37 GMT

The SharePoint Software Factory is a Visual Studio Extension helping SharePoint newbies, as well as experienced developers to create, manage and deploy SharePoint solutions without having to know every tiny XML and C# secret.

SPSF provides a huge collection of helpful recipes for development, debugging and deployment of SharePoint standard artifacts and is fully compatible with SharePoint 2007/2010/2013 and Visual Studio 2008/2010/2012.

News

2013-04-29 Recommended update. Several bugs fixed, improved SP2013 supporty (Release Notes)
2013-03-27 Fixed bug which caused resources in _layouts folder to be linked falsely (Release Notes)
2013-03-17 First beta release for Visual Studio 2012 and SharePoint 2010/2013 (Release Notes)
2012-02-13 New version 3.2 released with new recipes (BCS import, Linq to SharePoint, CAS Policies etc.) and several fixes (Release Notes)

For updates on SPSF follow us on Twitter or visit our blogs (links at the end of the page)

Resources

HowTo's

Supported Configurations

	Visual Studio 2012	Visual Studio 2010	Visual Studio 2008 (english)
SharePoint 2013	yes	no	no
SharePoint 2010	yes	yes	yes
SharePoint 2007	no	yes	yes

Key Features

Get started with professional SharePoint development in less than 5 mins! more
Use powerful wizards to create all important SharePoint artifacts more
Fully integrated in Visual Studio more
Refactoring of artifacts (i.e. Content Types) more
Fully automated build system creates web solutions packages (“WSP”s) and deployment files
Integrated Code quality checks in “Release” build (additional installs required)
All projects are self maintained, meaning that there is no dependency to having SPSF installed on the machine, when you just want to build, or continue development without SPSF
Standard VS2010/VS2013 item templates for SharePoint development can be used together with SPSF projects, though the coding conventions have to be applied by the developers for these items
Extensive Help available directly from Visual Studio or online
Supports SharePoint Visual Studio application structure but also “old” best-practice SharePoint Hive structure (limited to VS2008/VS2010) more
Supports SharePoint 2007/2010/2013 and Visual Studio 2008/2010/2012
Upgrade existing SharePoint projects more

Now download, install and get started with SharePoint development!!!
See Screenshots of SPSF

Video

VS2010 version of SPSF.

Your support !!!

We will expand and improve SPSF over time. Our current primary focus is to increase support for SharePoint 2013.
If you want to support this project, you can either extend the SPSF with your own Guidance Package (just download the source code to see how it works) or provide us with ideas, code and feedback for new recipes, which we can include.
If you already have a project at CodePlex with code snippets, web part templates, code for SharePoint artifacts etc. please drop us a note if you want us to include it in SPSF.

About the Authors

Matthias Einig
Matthias works as team lead at Steria AB in Stockholm. He focuses on SharePoint solution architecture, development, application lifecycle management with Team Foundation Server and in general on improving the quality of custom SharePoint solutions.
Blog: www.matthiaseinig.de
Twitter: @mattein

Torsten Mandelkow
Torsten works at Microsoft in Germany and has a passion for high quality SharePoint Code. Starting with SPSF SharePoint Software Factory to make SharePoint development easier and more reusable he now focuses on automizing code quality analysis of SharePoint solutions.
Blog: blogs.msdn.com/b/torstenmandelkow/
Twitter: @tmandelkow

Updated Release: SPSF SharePoint Software Factory 4.1 (VS2012) (Apr 29, 2013)

matein78 — Mon, 29 Apr 2013 18:05:59 GMT

v4.1.2.2904 (2013-04-29)
New

New: Delegate control recipe now provides all new delegate controls in SP2013 projects
New: New ItemEventReceivers added for SP2013 projects

Changes

Updated: SharePointVersions.xml to include build numbers and names up till SP2013 CU April 2013
Changed: Set the SPCAF default rules to the "ExtendedRecommendedRules.spruleset" frp, SPCAF (includes SP2010/2013 compatibility check)
Changed License to the weaker MS-PL to make it easier to use SPSF in customer projects
Changed: Removed unnecessary detailed logging to c:\SPSF.log file
Updated: HowTo's in SPSF help

Fixes

Fixed: Encoding issue which happened in some environments with the PowerShell scripts of the deployment project (run "Update solution to current SPSF" recipe to fix existing projects)
Fixed: ItemEventReceivers recipe was not working correctly
Fixed: Site Column -> Person & Group was not setting "ShowField" property to "ImnName"
Fixed: List Definition property values for "Default" now in uppercase. "EnableModeration" remains CamelCase as requried by the XML schema
Fixed: Integrating SPCAF in local Release build failed in some cases (Get SPCAF)
Fixed: Integrating FxCop caused error in local Release build

v4.1.1.2493 (2013-03-27)
Fixes

Generated links to resources in the _layouts folder were not linked correctly in SP2013 projects. The links have to point to _layouts/15, _controltemplates/15 etc. see also http://matte.in/10On2L1
Due to a bug in Visual Studio, SharePoint projects which reside in a solution folder are missing the "Deploy" command. So currently SPSF creates all projects in the solution root instead.
Fixed error in recipe "Update Solution to current SPSF" when trying to crate the deployment project
Fixed wrong VS version in csproj file of resources projects

v4.1.0.7601 (2013-03-17)
Prerequisites

Visual Studio 2012
SharePoint 2010/2013
OpenGAX
MS Office Developer Tools for Visual Studio 2012

New

Added support for Visual Studio 2012
Added support for SharePoint 2013
New PowerShell based solution deployment package based SharePoint Solution Deployer
Added a deployment project recpide to allow multiple deployment projects
Integrated SPCAF SharePoint CodeAnalysis Framework
Integrated SPCop SharePoint CodeCheck
Added SP2013 MasterPage and PageLayout templates

Changes

Removed support for Visual Studio 2008/2010 (use SPSF 3.2)
Removed support for Hive project structure (use SPSF 3.2)
Removed support for MOSS2007
Renamed SharePointTargets.targets to SPSF.targets
Removed Farm Solution Deployment recipes (use VS or CKSDev instead), sandboxed solution and quick deploy are still included.
Removed debugging recipes (use VS or CKSDev instead)
Removed configuration project template
SharePoint project will still create WSP on every build but won't copy them to the deployment project
Deployment project collects all WSPs from the whole solution and has a build dependency on als SharePoint projects
Updated SharePoint version recipe to include all known SharePoint versions
Updated images to look nicer in VS2012
Selection treeviews now sorted and "[Elements in this solution]" is now on the top to find elements easier.
Improved general usability of dialogs/wizards

Fixes

Administration page recipe now generates designer.cs
Application page recipe now generates designer.cs
Uses any StyleCop Version
Fixed Feature Dependency dialog to show again "[Elements in this solution]"
Fixed Ribbon Tab Recipe
Fixed PSScript Recipe
Fixed Sequential Workflow not naming constructor correctly
Fixed multiple minor bugs and issues

Known Bugs

Project templates are not yet working, to add a new SharePoint project use the VS standard templates, move the project into the "Solutions" folder and run the "Update Project to current SPSF version" recipe
Site Definitions recipes are not yet updated to SP2013
The "Deploy" menuitem is missing due to a bug in VS2012 when SharePoint Projects are located in a solution folder
Some recipes create references to _layouts files in the default hive (14) instead of /15/ when creating artifacts for an SP2013 solution

Released: SPSF SharePoint Software Factory 4.1 (VS2012) (Apr 29, 2013)

Mon, 29 Apr 2013 18:05:59 GMT

v4.1.2.2904 (2013-04-29)
New

New: Delegate control recipe now provides all new delegate controls in SP2013 projects
New: New ItemEventReceivers added for SP2013 projects

Changes

Updated: SharePointVersions.xml to include build numbers and names up till SP2013 CU April 2013
Changed: Set the SPCAF default rules to the "ExtendedRecommendedRules.spruleset" frp, SPCAF (includes SP2010/2013 compatibility check)
Changed License to the weaker MS-PL to make it easier to use SPSF in customer projects
Changed: Removed unnecessary detailed logging to c:\SPSF.log file
Updated: HowTo's in SPSF help

Fixes

Fixed: Encoding issue which happened in some environments with the PowerShell scripts of the deployment project (run "Update solution to current SPSF" recipe to fix existing projects)
Fixed: ItemEventReceivers recipe was not working correctly
Fixed: Site Column -> Person & Group was not setting "ShowField" property to "ImnName"
Fixed: List Definition property values for "Default" now in uppercase. "EnableModeration" remains CamelCase as requried by the XML schema
Fixed: Integrating SPCAF in local Release build failed in some cases (Get SPCAF)
Fixed: Integrating FxCop caused error in local Release build

v4.1.1.2493 (2013-03-27)
Fixes

Generated links to resources in the _layouts folder were not linked correctly in SP2013 projects. The links have to point to _layouts/15, _controltemplates/15 etc. see also http://matte.in/10On2L1
Due to a bug in Visual Studio, SharePoint projects which reside in a solution folder are missing the "Deploy" command. So currently SPSF creates all projects in the solution root instead.
Fixed error in recipe "Update Solution to current SPSF" when trying to crate the deployment project
Fixed wrong VS version in csproj file of resources projects

v4.1.0.7601 (2013-03-17)
Prerequisites

Visual Studio 2012
SharePoint 2010/2013
OpenGAX
MS Office Developer Tools for Visual Studio 2012

New

Added support for Visual Studio 2012
Added support for SharePoint 2013
New PowerShell based solution deployment package based SharePoint Solution Deployer
Added a deployment project recpide to allow multiple deployment projects
Integrated SPCAF SharePoint CodeAnalysis Framework
Integrated SPCop SharePoint CodeCheck
Added SP2013 MasterPage and PageLayout templates

Changes

Removed support for Visual Studio 2008/2010 (use SPSF 3.2)
Removed support for Hive project structure (use SPSF 3.2)
Removed support for MOSS2007
Renamed SharePointTargets.targets to SPSF.targets
Removed Farm Solution Deployment recipes (use VS or CKSDev instead), sandboxed solution and quick deploy are still included.
Removed debugging recipes (use VS or CKSDev instead)
Removed configuration project template
SharePoint project will still create WSP on every build but won't copy them to the deployment project
Deployment project collects all WSPs from the whole solution and has a build dependency on als SharePoint projects
Updated SharePoint version recipe to include all known SharePoint versions
Updated images to look nicer in VS2012
Selection treeviews now sorted and "[Elements in this solution]" is now on the top to find elements easier.
Improved general usability of dialogs/wizards

Fixes

Administration page recipe now generates designer.cs
Application page recipe now generates designer.cs
Uses any StyleCop Version
Fixed Feature Dependency dialog to show again "[Elements in this solution]"
Fixed Ribbon Tab Recipe
Fixed PSScript Recipe
Fixed Sequential Workflow not naming constructor correctly
Fixed multiple minor bugs and issues

Known Bugs

Project templates are not yet working, to add a new SharePoint project use the VS standard templates, move the project into the "Solutions" folder and run the "Update Project to current SPSF version" recipe
Site Definitions recipes are not yet updated to SP2013
The "Deploy" menuitem is missing due to a bug in VS2012 when SharePoint Projects are located in a solution folder
Some recipes create references to _layouts files in the default hive (14) instead of /15/ when creating artifacts for an SP2013 solution

Updated Wiki: Home

matein78 — Fri, 26 Apr 2013 14:17:52 GMT

News

2013-03-27 Fixed bug which caused resources in _layouts folder to be linked falsely (Release Notes)
2013-03-17 First beta release for Visual Studio 2012 and SharePoint 2010/2013 (Release Notes)
2012-02-13 New version 3.2 released with new recipes (BCS import, Linq to SharePoint, CAS Policies etc.) and several fixes (Release Notes)

For updates on SPSF follow us on Twitter or visit our blogs (links at the end of the page)

Resources

HowTo's

Supported Configurations

	Visual Studio 2012	Visual Studio 2010	Visual Studio 2008 (english)
SharePoint 2013	yes	no	no
SharePoint 2010	yes	yes	yes
SharePoint 2007	no	yes	yes

Key Features

Get started with professional SharePoint development in less than 5 mins! more
Use powerful wizards to create all important SharePoint artifacts more
Fully integrated in Visual Studio more
Refactoring of artifacts (i.e. Content Types) more
Fully automated build system creates web solutions packages (“WSP”s) and deployment files
Integrated Code quality checks in “Release” build (additional installs required)
All projects are self maintained, meaning that there is no dependency to having SPSF installed on the machine, when you just want to build, or continue development without SPSF
Standard VS2010/VS2013 item templates for SharePoint development can be used together with SPSF projects, though the coding conventions have to be applied by the developers for these items
Extensive Help available directly from Visual Studio or online
Supports SharePoint Visual Studio application structure but also “old” best-practice SharePoint Hive structure (limited to VS2008/VS2010) more
Supports SharePoint 2007/2010/2013 and Visual Studio 2008/2010/2012
Upgrade existing SharePoint projects more

Now download, install and get started with SharePoint development!!!
See Screenshots of SPSF

Video

VS2010 version of SPSF.

Your support !!!

About the Authors

Project License Changed

Tue, 16 Apr 2013 20:08:04 GMT

Microsoft Public License (Ms-PL) This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software. 1. Definitions The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here as under U.S. copyright law. A "contribution" is the original software, or any additions or changes to the software. A "contributor" is any person that distributes its contribution under this license. "Licensed patents" are a contributor's patent claims that read directly on its contribution. 2. Grant of Rights (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create. (B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software. 3. Conditions and Limitations (A) No Trademark License- This license does not grant you rights to use any contributors' name, logo, or trademarks. (B) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically. (C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software. (D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license. (E) The software is licensed "as-is." You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.