spsf Issue Tracker Rss Feed

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.

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()

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.

Commented Feature: Filedtype Managed Metadata [6283]

SvenW — Thu, 11 Apr 2013 12:08:49 GMT

Note to myself :-) Extend fieldtype recipies with managed metadata fieldtype

Sample project and details

http://www.sharepointconfig.com/2011/03/issues-provisioning-sharepoint-2010-managed-metadata-fields/
http://www.sharepointconfig.com/2011/03/the-complete-guide-to-provisioning-sharepoint-2010-managed-metadata-fields/
Comments: ** Comment from web user: SvenW **

*Ping* any update on this one?

Commented Issue: "Deploy" missing from context menu [7369]

matein78 — Fri, 29 Mar 2013 10:03:12 GMT

The default "Deploy" context menu item is missing due to a bug of the Office Developer Tools for VS2012

The bug relates to projects which are placed in a solution folder (this is the default case for SPSF Projects).
As soon as you move the project into the VS solution root, the menu item appears again.

Deploying by pressing F5 still works even if the projects are in subfolders.
This is a bug of VS2012, so we don't have a current solution of fixing that.

As workaround move the projects to the solution root. SPSF will still work as usual.
Comments: ** Comment from web user: matein78 **

Temporarily resolved in 4.1.1.2493 by not using VS solution folder by default anymore...
As soon as the bug is fixed in VS2012 the previous behaviour will be restored

Closed Issue: Img references on SP2013 into wrong _layouts folder [7367]

matein78 — Fri, 29 Mar 2013 10:02:15 GMT

When generating files with SPSF for a SP2013 Project, some references to _layouts files don't reference the file in "_layouts/15/" but instead of "_layouts/" which points to the 14 hive.

Result:
The image cannot be found.
We are working on it to fix that asap.

Commented Issue: Img references on SP2013 into wrong _layouts folder [7367]

matein78 — Fri, 29 Mar 2013 10:02:05 GMT

Fixed in 4.1.1.2493

Created Issue: "Deploy" missing from context menu [7369]

matein78 — Mon, 25 Mar 2013 11:01:23 GMT

Created Issue: Img references on SP2013 into wrong _layouts folder [7367]

matein78 — Mon, 25 Mar 2013 10:56:58 GMT

Closed Issue: Feature (visibility) dependency dialog does not show solution features [6030]

matein78 — Mon, 18 Mar 2013 06:30:14 GMT

During the creation process of a new site-definition one can choose the visibility dependency from a list of features. Unfortunately the features contained in the current solution are not shown. Of course I can change it manually in my webtemp later, but
... :)

Again greetings and thx for spfs!

Commented Issue: Feature (visibility) dependency dialog does not show solution features [6030]

matein78 — Mon, 18 Mar 2013 06:30:03 GMT

Fixed in SPSF4.1 for VS2012

Closed Issue: Feature dependency [6158]

matein78 — Mon, 18 Mar 2013 06:27:13 GMT

When creating a new feature I am unable to set a dependency on a feature that is in my project.