SPSF SharePoint Software Factory 4.1 (VS2012)

Rating:        Based on 1 rating
Reviewed:  1 review
Downloads: 1744
Released: Apr 29, 2013
Updated: Apr 29, 2013 by matein78
Dev status: Stable Help Icon

Downloads

Application SPALM.SPSF.4.1.2.2904.vsix
application, 13903K, uploaded Apr 29 - 1115 downloads
Documentation SPSF_Documentation.pdf
documentation, 2837K, uploaded Apr 29 - 629 downloads

Release Notes

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 New 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

Reviews for this release

     
I am using it since long time, save me lot of time. The best design tool for SharePoint.
by MichelCapdevila on Mar 17 at 10:07 AM