We did a recent migration from 2007 to 2010, medium sized project (Silverlight webparts, 30+ other webparts, wfc, images, js, list defintions, Feature receivers and lot more). We converted all the webparts to Visual WebParts (we determined Farm Solution is ok), including namespace conventions. (Had to recreate webparts in publishing pages though). We also ...
My team has converted a large SP2007 WSP builder project to SharePoint 2010. A few important things to remember especially if you are upgrading the sharepoint content database as well:
When recreating features remember to use the same feature ids.
Do not change assembly names, namespaces for things like webparts and eventreceivers and other things that are ...
I have migrated a solution with more than one feature and some assets deployed to the layouts folder from 2007 to 2010. I was happy with the out of the box experience in Visual Studio 2010 after I got used to it. The migration was a bit more manual than I expected at first, but overall, not overly complex. I recommend starting the migration with the Out of ...
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 ...
Ok, first are both checkboxes at the bottom marked ("Show processes from all users" and "Show processes in all sessions")? If so, maybe you changed the type of code shown under the "Attach to:" field. I would dig through these three settings.
If you still can't find the process after that, try an old fashioned reboot.
Firstly, if you are using SP2010, and VS2010 - you might want to think about using the in built SharePoint tooling rather than WSPBuilder.
Secondly, before you will see the webpart you need to enable the feature containing it at the Web or Site level as it has been scoped. Go to Site features within /_layouts/settings.aspx and ensure that the feature ...
You need to create the directory structure in your solution for WSPBuilder to package & deploy it correctly.
The structure will be something like:
Once you've got that, you can create new ASP.NET Web Forms in that folder, and they'll be deployed with the WSP.
The URL to access them will be something like
This is purely opinion and conjecture, so I suggest this be community wiki
This opinion is further down entirely to the dynamics of the market you operate in or the customers that you serve, but I have found it far more economical and simpler to freeze continual development in SP2007 and build only for SP2010.
Continue to support customers on SP2007 by ...
If your DLL is placed in the bin\debug or bin\release folders of your project (e.g. "Copy Local" equal to true for your DLL Reference), the DLL will automatically be included in your WSP and deploy according to the DeploymentTarget of your local WSPBuilder.exe.config file.
If you are sharing the same DLL across multiple projects, it might make more sense ...
Not enough information to suggest a solution, but here are a few links --
One of a former project I worked on, I use a custom site template to hide features to other site collections.
The idea is to follow these steps :
create a custom site template specific to your application. I often use to starts from the blank site definition to start from scratch (but it can depends on your requirements)
create all features related to your ...
You should deploy your DLLs to GAC, if you are using some external DLLs for your project you should include them in your wsp and add them to GAC also, make sure the manifest.xml file of the solution (inside wsp) has following lines
<Assembly DeploymentTarget="GlobalAssemblyCache" Location="YourProject.dll" />
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 ...
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,
<!-- Solution created by WSPBuilder. 28/06/2013 09:21:25 -->
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
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!
also, your using 2013 which is different to 2010 but you could give it ago! things have changed from 2010 ...
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
The descriptions says:
A SharePoint Solution Package (WSP) ...
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....
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.
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 ...
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:
Arsalan Adam Khatri
I strongly recommend you look at some tutorials for introductory web part development in SharePoint 2010, and also look at how to create List Instances from Features. Both are pretty standard tasks when it comes to development.
Here's a full tutorial on creating a web part in Visual Studio 2010.
List Instances are standard, out of the box Visual Studio ...