7

Your plan is good, and respects good practices (at least the practices I've been following for ages). Your approach is to: Create the solution in VS Create one feature (scope: Web) Create two classes for the event receivers (both inheriting from SPItemEventReceiver) Add a feature event receiver on the feature (inheriting from SPFeatureReceiver) In the ...


2

Inside Visual Studio, try to switch off assembly inclusion: Then republish and re-upload template once again.


2

You can (also) use Visual Studio to Import and modify your WSP. Have a look at this link from Microsoft (For 2010 but still working for 2013): Importing the .wsp File in few step : Create a VS project from type : Import SharePoint Solution Package Choose your WSP (after it will create the SharePoint project with all files/elements of you wsp make your ...


1

You can do that from PowerShell. For that purpose you need small but extremely helpful library called 'CabLib'. It's included as part of the wspbuilder (old tool to build and pack projects for SharePoint 2007). You need to download CabLib.dll from here - WSPBuilder Extensions 1.0.6. Under the downloads select "CabLib.dll for x64 systems (version: 10.5)" ...


1

It is possible, you'll have to replicate steps that Visual Studio automagically do for you ). Extract wsps. Because .wsp is .cab archive, you'll need a tool to deal with cabs. I used Total Commander plugin for the purpose. Extract into separate folders. Merge content of manifest.xml from those folders into one manifest.xml Merge files from those folders (...


1

For extracting you can use Solution Extractor Tool from below link http://blogs.technet.com/b/patrick_heyde/archive/2009/08/28/how-to-extract-wsp-files-from-sharepoint.aspx Once you have extracted the wsp. You can use PowerShell for installing it into your SharePoint 2010 environment. Add-SPSolution c:\path\wspname.wsp Install-SPSolution –Identity ...


1

add this just above your public class file! [SharePointPermissionAttribute(System.Security.Permissions.SecurityAction.Demand, Impersonate = true)] [SharePointPermissionAttribute(System.Security.Permissions.SecurityAction.Demand, ObjectModel = true)] then let wspbuilder do the rest for you as it will build the xml file for you within the manifest file! ...


1

Find your solution file with extension .wsp Change solution extension to .CAB Now open this file and you will see different files in it but the one you need to deal with is manifest.xml This is how a manifest.xml file created by WSP Builder looks like, <?xml version="1.0"?> <!-- Solution created by WSPBuilder. 28/06/2013 09:21:25 --> &...


1

Maybe this wil help. There are some things you have to check: 1.If Package has SharePoint Product Version set to 15.0 2.Your project is build on .net 4.5 3.You are not deploying on a different farm 4.You are referencing the right sharepoint 2013 assemblies


1

dont listen to Luis, well most of it ;) , wspbuilder is brill for 2003 and 2007! for 2010 make sure you have the correct version! you need WSPBuilder Extensions 2010 BETA 1.4 which is at the bottom! http://wspbuilder.codeplex.com/releases/view/30858 also, your using 2013 which is different to 2010 but you could give it ago! things have changed from 2010 ...


1

DROP WSPBuilder, not a good thing, you need to do the webparts with visual studio, thats it. It will create all the files for you, also you have to create a Feature that deploys the webpart. WSPBuilder is WAY OOOOOOOOOLD!, Avoid it Last Update was on May 9th 2009 https://wspbuilder.codeplex.com/ The descriptions says: A SharePoint Solution Package (WSP) ...


1

Did you install visual studio? If so, did you install the Microsoft Office Developer Tools for Visual Studio 2012?? Once you've done that you can create a new SharePoint project and when when you compile it will create the wsp for you and put it in the bin folder. See here: http://msdn.microsoft.com/en-us/library/ee554869.aspx and here: http://msdn....


1

WSPBuilder will only allows Safe Controls entries for objects that inherits from the "Control" class. A simple fix could be to create an empty class that inherits from WebControl and use the same namespace in your fake ascx file.


1

to change it you would need to change the project name in solution explorer, click on it once so its higlighted and then click on it again to rename or rightclick and then select rename, also the solution. Next step isto click on project again and rightclick, this time select properties and change the assembly name and default nasespace giving them the ...


1

WSP Builder uses WSPBuilder.exe.config file to create wsp and set all properties... This link should help changing the name and other properties of wsp: http://weblogs.asp.net/bsimser/archive/2009/11/26/name-that-wsp-sharepoint-developer-tricks-with-wspbuilder.aspx Arsalan Adam Khatri


Only top voted, non community-wiki answers of a minimum length are eligible