Skip to main content

Transfer SharePoint solution from VS 2008 to VS 2010


There is a solution for SharePoint created in Visual Studio 2008 for SharePoint 2007. The task is to transfer this application to Visual Studio 2010 in order to deploy the same functionality on SharePoint 2010.

Initial solution structure

1. List Event Handler
2. Feature that on activating: creates a sub-site, content types, lists and initial data, registers list event handler for the list and sets up permissions for the sub-site
3. Web Part
4. Application page which is deployed to _LAYOUTS folder and where the Web Part is displayed.

Ok girls and boys, the process

1. Create a new project of type Empty SharePoint Project in Visual Studio 2010:

2. When the project is being created select a "Deploy as farm solution" option:

3. Empty project created! Now we will add List Event Handler:

We choose Custom List as a list type and "An item is being updated" as an event type to handle:

The full list of available event types is as follows:

Here we go - new event handler was added:

4. Now we add a new feature to our project by selecting "Add Feature" command in the context menu for Features node in Solution Explorer:

5. Good, new features was added and we can see the following screen to manage our new feature:

6. We rename the feature in Soultion Explorer and then add an Event Receiver:

When Event receiver is added I put all the code from my initial Feature Event Receiver. It just worked, because the API I used is fully compatible with SharePoint 2010.

I have just made one change though. My initial code contained the List Event Handler registration logic as follows:

string assemblyName = "SlavasAssembly, Version=, Culture=neutral, PublicKeyToken=11a1bcd111e1111f";

string itemReceiverName = "EventHandlerClassNameWithNamespace";

list.EventReceivers.Add(SPEventReceiverType.ItemUpdating, assemblyName, itemReceiverName);
What we can do in SharePoint 2010 is using the $SharePoint.Project.AssemblyFullName$ expression instead of the real assembly. So what I have done is put:
string assemblyName = "$SharePoint.Project.AssemblyFullName$";
It's very handy, because it saves time. Otherwise I would use some tools like this one - - to generate PublicKeyToken.
7. Then we will add a Web Part:

I have just copied my source code from initial solution to the new Web part source code as before.

If we look at the .webpart file we will see that assembly name expression again:

8. Adding application page. First we have to add Layouts mapped folder to our solution:

It's very good, because now if the folder changes from 12 to 14 or 16 it doesn't really matter to us, because it will be server relevant and not hard-coded.

9. Adding application page. In the Layouts folder context menu choose Add New Item command and you will see the following options. Select Application Page:

Because I have some custom import directives to use my functionality on the application page I copied the initial source code, but change the directives to use $SharePoint.Project.AssemblyFullName$ expression:

10. Right. Now packaging and installer creation. Packaging is easy, just choose Package command for the solution:

When this is done you can see the .wsp file created in your bin directory for the solution. This is your package.

For installer I used the following Power Shell comands:

Add-SPSolution -LiteralPath SlavasSolution.wsp
Install-SPSolution -Identity SlavasSolution.wsp -WebApplication -GACDeployment
Cool. All done. I can now use my solution on SharePoint 2010 server! :)
Stay tuned.


Popular posts from this blog

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server.

According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition.
The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you wou…

SharePoint 2010 Search Issue - FQDN Crawl

I have recently set up a standalone SharePoint 2010 environment.

The Web application was created with host header and the site collection is accessible from the client machines, but not internally. That was because of using FQDN to access the Web site.

The error when I tried to access site internally was similar to the one described here:

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version

And the search returned the following error in the Event Log:

"The start address cannot be crawled.

Context: Application 'Search_Service_Application', Catalog 'Portal_Content'

Details: This item could not be crawled because the crawler could not connect to the repository."

One of the suggestions was to disable the loopback check, but that would compromise the Web server.

So what I have done was:

1. Added a binding to my IIS Web site for a different port. Let's say my Web server name is win-v7m…

SharePoint 2013 - Setting Up External Content Type

There were earlier posts where we discussed External Content Types setup for SharePoint 2010:

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

External Content Types - Reload - Setting up for SQL Server database using SQL Server authentication - SharePoint 2010 Server

This one is about creating connection to the custom SQL Server database (External System) in SharePoint 2013.

1. Create Secure Store Service Target Application

1.1. Go to Central Administration -> Manage Service Applications -> Secure Store Service Application. Click "Generate New Key" if required:

1.2. Provide Pass Phrase:

1.3. Create "New" to create new Target Application:

1.4. Provide the name and other parameters and click "Next":

Note: It's good idea to specify "Group" for Target Application Type. In that case you would be able to manage access to the external data using Active Directory groups rather …