Click here to Skip to main content
14,767,956 members
Articles » Enterprise Systems » SharePoint Server » General
Posted 27 Nov 2007


153 bookmarked

Converting an ASP.NET site into a SharePoint site

Rate me:
Please Sign up or sign in to vote.
4.81/5 (30 votes)
3 Apr 2008CPOL
This article will show how to convert an existing ASP.NET application into a SharePoint site using the same look and feel of the SharePoint site.


There are a lot of ASP.NET web developers who are moving to SharePoint site creation. This article will explain in detail how an ASP.NET webpage developed in Visual Studio can be converted into a SharePoint site. If there is a requirement for a website created in Visual Studio, just the old fashioned way with the code-behind logic and other layers like Data Access and Business Logic, to be converted into a SharePoint site, and still make it work the same way with the same code-behind, you are in the right place. This article deals with right that.


There is an ASP.NET website solution that contains three layers viz. Code-Behind Layer, Business-Logic Layer, and the Data-Access Layer. The website has functionality implemented in all these layers. The Business-Logic and the Data-Access layers are in a different Class Library project. We have to convert this website into a SharePoint site. Also, we want to use the same look and feel of the SharePoint site. So, we have to use the SharePoint master page instead of the one that we are having (we can also use our own master page; just that you have to add some default Place Holders that are required for the SharePoint functionalities). In this article, we are dealing with a website with the same look and feel as a SharePoint site.

Steps Overview

There are three steps that are explained in the article which will help you to transform your ASP.NET Web Application into a SharePoint site.

Step1: Add a Web Deployment Project to your website solution that will create a single DLL for the website. This step will give us the code-behind DLL and other dependency DLLs for the website.

Step2: Copy the bin folder items (DLLs) into the SharePoint site, and tweak the web configuration file of the SharePoint site to use the copied DLLs.

Step3: Open your created SharePoint site in SharePoint Designer and import the web pages from our web application and link it to the appropriate DLLs.

Step 1: Adding a web deployment project to your website solution that will create a single DLL for the website

  1. The first step is to make sure you have added the proper namespaces and avoided class name duplications within a namespace before going to step 2.
  2. Add a web deployment project into your website solution. This can be done by right clicking on the website project and choosing 'Add Web Deployment Project' option.
  3. Note: This option will be available once you have installed the Web Deployment Setup.

  4. Add a strong name key to the solution which we will be using to sign all the DLLs.
  5. Now, we have to set the deployment project properties. Right-click on the deployment project and click 'Property Pages'.
  6. Go to the 'Output Assemblies' tab, and choose the 'Merge all assemblies to single assembly' option (this is the default option), and give the assembly name.
  7. Screenshot - output_assembly-Pic1.jpg

  8. Next, go to the Signing tab and choose the 'Enable strong naming' option, and choose the strong name key that you have created in step 3.
  9. Screenshot - signing-pic2.jpg

  10. Also check the option 'Mark the assemblies with AllowPartiallyTrustedCallersAttribute (APTCA)'. This will make the DLL partially trusted, and thus the SharePoint site can use them. Click on OK.
  11. The Data Access, Business Logic, or any other assemblies that are a dependency to the web application must be strong named with a strong name key.
  12. Screenshot - assemblyinfo-pic3.jpg

  13. Also, we have to allow partially trusted callers for the dependency DLLs. This can be done by opening the file of the Class Library project and putting the following line of code as shown above:
  14. [assembly: System.Security.AllowPartiallyTrustedCallers]
  15. Build the deployment project under Release mode (any mode).
  16. Go to the path where the deployment project has put the output. Here, in the bin directory, you will find the web deployment DLL file. If there are any dependency projects such as the Business Layer and the Data-Access Layer, those DLLs also will be copied to this bin folder.

Now, we have the DLLs that can be used in our SharePoint site for using the same functionality as in our ASP.NET site.

Step 2: Copy the bin folder items (DLLs) into the SharePoint site and tweak the web configuration file of the SharePoint site to use the copied DLLs

The next step in our SharePoint site creation is linking the DLLs that we have created in the procedure above into our already existing blank SharePoint site. There are also some changes that are required in our SharePoint site's web.config file (By default found in C:\Inetpub\wwwroot\wss\VirtualDirectories\<PortNo>). Following are the steps that has to be done:

  1. Copy the bin folder contents from your ASP.NET deployment folder into the bin folder of your SharePoint site (usually in C:\Inetpub\wwwroot\wss\VirtualDirectories\<PortNo>\bin).
  2. Open the web.config file of your SharePoint site.
  3. Add the following line in under the <PageParserPath> section:
  4. <PageParserPath VirtualPath="/*" CompilationMode="Always" 
       AllowServerSideScript="true" IncludeSubFolders="true" />
  5. Register the assemblies that will be used in the SharePoint site (web deployment DLL which has the code-behind code, the Business Layer and Data Access DLLs) as a SafeControl. For this, add the following under the <SafeControls> section:
  6. <SafeControl Assembly="SampleWebSiteAssembly" 
       Namespace="SampleSiteNamespace" TypeName="*" Safe="True" />
  7. Also add all the other dependency DLLs that your site will be using. Note that all these DLLs must be strong named and marked AllowPartiallyTrusted.
  8. Change the trust level from Minimal to Medium by changing the level attribute of the <trust> section from 'WSS_Minimal' to 'WSS_Medium'.
  9. Note: You can also do the following to enable the original errors being shown in the SharePoint site screen for easy error identification. You have to change the mode attribute of the <customErrors> section to Off. Also, change the CallStack attribute of the <SafeMode> section to True.

Step 3: Open your created SharePoint site in SharePoint Designer and import the web pages from our web application

Let us say we have a link in our SharePoint site in the left navigation panel, on the click of which you want to display one of your ASP.NET pages in the content place holder of the SharePoint site. This is what we do:

  1. Open your SharePoint site in the SharePoint Designer (in this article, we are using SharePoint Designer 2007).
  2. Click on File-->Import-->File. This will open the Import dialog box.
  3. Click on 'Add File' and choose the ASPX page that you have created from your local folder. Please note that you have to take the ASPX file from the deployment folder and not the ASPX page that is there in the project. Click OK. This will import the page into your SharePoint site.
  4. Now, double-click on the newly imported page. Click on the Split option in the Design/Split/Code option in the centre pane (bottom left of the pane).
  5. As soon as you do this, you will see in the designer window an error that says: The Master Page file cannot be loaded. This is because the master file that we have used in the project is different from the master page that the SharePoint site uses. You can either import the master page or use SharePoint's default master page. In this article, we are going to use SharePoint's default master page.
  6. Change the 'MasterPageFile' attribute in the Page directive of the web page to a value same as the default.aspx in the SharePoint site, which is ~masterurl/default.master.
  7. Delete the 'CodeFile' attribute from the Page directive as this is only for Visual Studio purposes.
  8. Now, change the ContentPlaceHolderID of the place holders in the ASP.NET page to a relevant SharePoint site place holder. For example, the ContenPlaceHolderID of the main content place holder of the ASP.NET page must be changed to 'PlaceHolderMain'.
  9. After mapping the place holders of the ASP.NET page to that of the SharePoint master page, the page will render in the design view with the default master page.
  10. Now, we have to change the Inherits attribute to add the assembly name. For example, if the namespace is 'SampleSiteNamespace' and the assembly name that the page uses for code-behind is SampleWebSiteAssembly, then we set Inherits="SampleSiteNamespace.SampleWebSiteAssembly", and this assembly must be in the bin of the SharePoint site as added in Step 2 above.

Now, we have our ASP.NET site as a SharePoint site, ready to run with the same look and feel of the SharePoint site.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

India India
I am a .NET/Sharepoint and Project Server Consultant. I hold Microsoft Technology Specialist certifications on ASP.NET 3.5 and Sharepoint 2007 Application Development

Comments and Discussions

QuestionConvert MVC Application ? Pin
Sr.GaneshRam5-Apr-18 1:59
MemberSr.GaneshRam5-Apr-18 1:59 
Questioncan we use loayout for this purpose Pin
aasif iqbal23-Jan-13 21:38
Memberaasif iqbal23-Jan-13 21:38 
QuestionError while trying to browse the page Pin
Member 946817728-Sep-12 4:27
MemberMember 946817728-Sep-12 4:27 
QuestionPros and Con of - developing new site in sharepoint vs developing site and converting into sharepoint site Pin
xchsdfghsfgsdfgsdfg9-Feb-12 20:27
Memberxchsdfghsfgsdfgsdfg9-Feb-12 20:27 
QuestionBeginning SharePoint Pin
Nits13511-Oct-11 7:10
MemberNits13511-Oct-11 7:10 
GeneralMy vote of 4 Pin
Amir Mehrabi-Jorshari27-Sep-10 11:29
MemberAmir Mehrabi-Jorshari27-Sep-10 11:29 
GeneralMy vote of 4 Pin
Biju VA15-Jul-10 1:05
professionalBiju VA15-Jul-10 1:05 
GeneralConverting website to sharepoint website Pin
Member 24079038-Mar-10 2:10
MemberMember 24079038-Mar-10 2:10 
GeneralServer block is not well Pin
gayajegg22-Feb-10 14:57
Membergayajegg22-Feb-10 14:57 
GeneralAn error occurred during the processing of . The attribute 'autoeventwireup' is not allowed in this page. Pin
gayajegg22-Feb-10 14:13
Membergayajegg22-Feb-10 14:13 
GeneralRe: An error occurred during the processing of . The attribute 'autoeventwireup' is not allowed in this page. Pin
gayajegg22-Feb-10 14:58
Membergayajegg22-Feb-10 14:58 
General.xsd files Pin
ajingar3-Feb-10 4:43
Memberajingar3-Feb-10 4:43 
AnswerRe: .xsd files Pin
srivatsan243-Feb-10 17:41
Membersrivatsan243-Feb-10 17:41 
Generalaspx page not populating in IIS Pin
shibu.sebastian11-Jan-10 7:55
Membershibu.sebastian11-Jan-10 7:55 
AnswerRe: aspx page not populating in IIS Pin
srivatsan2411-Jan-10 18:01
Membersrivatsan2411-Jan-10 18:01 web application not workong on sharepoint. global.asax problem [modified] Pin
shibu.sebastian6-Jan-10 1:00
Membershibu.sebastian6-Jan-10 1:00 
GeneralConverting web application with events and &lt;% code Pin
mmfriederick13-Dec-09 9:46
Membermmfriederick13-Dec-09 9:46 
GeneralNot able to run Website on Share point Pin
mailneerajsehgal5-Nov-09 20:36
Membermailneerajsehgal5-Nov-09 20:36 
QuestionNo Namespace Pin
ajingar2-Oct-09 7:37
Memberajingar2-Oct-09 7:37 
AnswerRe: No Namespace Pin
srivatsan242-Oct-09 12:12
Membersrivatsan242-Oct-09 12:12 
QuestionRe: No Namespace Pin
ajingar4-Oct-09 12:31
Memberajingar4-Oct-09 12:31 
AnswerRe: No Namespace Pin
srivatsan244-Oct-09 13:39
Membersrivatsan244-Oct-09 13:39 
QuestionRe: No Namespace Pin
ajingar5-Oct-09 1:22
Memberajingar5-Oct-09 1:22 
AnswerRe: No Namespace [modified] Pin
ajingar5-Oct-09 3:12
Memberajingar5-Oct-09 3:12 
GeneralToo much Words! [modified] Pin
cl.kcitwm12-Aug-09 18:43
Membercl.kcitwm12-Aug-09 18:43 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.