Could not load file or assembly ‘Microsoft.Sharepoint.Sandbox, Version=14.0.0.0

Could not load file or assembly ‘Microsoft.Sharepoint.Sandbox, Version=14.0.0.0, …………..
Posted: June 25, 2013 in SharePoint 2010, Technical Diary
Tags: 'Microsoft.Sharepoint.Sandbox, Could not load file or assembly, DLL Erro, SharePoint2010, Version=14.0.0.0
0

Assembly error in ASP.Net Web Application during Run Time
 “Could not load file or assembly ‘Microsoft.Sharepoint.Sandbox, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. An attempt was made to load a program with an incorrect format.”
Issue
I created an ASP.Net Web Application. I added a reference to the “Microsoft.SharePoint.dll”. I needed this to use some of the SharePoint Server Object Model assemblies.

 The application was built successfully, however at runtime it threw the following error –


On investigating I found that a “Microsoft.Sharepoint.Sandbox.dll” was created in the bin folder of my Web application.
 An instinctive though that would come to the mind of all would be – “I have not added a reference to this dll, then what is it doing in my bin folder”. Then naturally we go ahead and delete it, with a hope that the problem is solved.
 But lo and behold! When we build our solution, a new copy of the dl is recreated in our bin folder. So the problem remains as is.
Root Cause
I am not sure, but it appears that when we reference the “Microsoft.SharePoint.dll” , on running the application, the assemblies in this dll, internally reference the “Microsoft.Sharepoint.Sandbox.dll”.
Please note this is my analysis and understanding only.
 Solution
Hence we see we should not be deleting this dll, it simply won’t work. We would need this dll and its assemblies to fully make use of the Server Object Model.
The most effective and logical solution is to make a local copy of this dll and add a reference to it in our Web Application.
 Here are the steps that I followed –
 Step 1
Make a copy of the Microsoft.SharePoint.Sandbox.dll from GAC to the local drive.
In the ‘Run’ use the following script –
%windir%\assembly\GAC_64\Microsoft.Sharepoint.Sandbox\14.0.0.0__71e9bce111e9429c

Step 2
Add a reference to this local copy of the dll, in your web application.

Step 3
Set the “copy to local” property to False.

Step 4
Build and Run the project.
It should work fine now.


Comments

Post a Comment

Popular posts from this blog

Sending email using Powershell script

Image
 Below is a script that can be used to send email using Powershell. If ((Get-PSSnapIn -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue) -eq $null )   { Add-PSSnapIn -Name Microsoft.SharePoint.PowerShell } $currentDate = Get-Date -Format g $HeaderOne $HeaderTwo $HeaderThree $HeaderFour $Outputreport = "<HTML><TITLE> Test E-Mail notification </TITLE> <head> <style>body {font-family: Calibri;font-size: 14px;}table {border-collapse: collapse;}table, th, td {border: 1px solid black;font-family: Calibri,Verdana;font-size: 14px;}th {background-color: #4CAF50;color:white;}</style></head>                      <BODY>                                           <H2> Test E-Mail notification on $($currentDate) CET </H2>  ...
Read more

Convert List Collection to DataTable using C#

public System.Data.DataTable ConvertToDataTable<T>(IList<T> data)         {             PropertyDescriptorCollection properties =                TypeDescriptor.GetProperties(typeof(T));             System.Data.DataTable table = new System.Data.DataTable();             foreach (PropertyDescriptor prop in properties)                 table.Columns.Add(prop.Name, Nullable.GetUnderlyingType(prop.PropertyType) ?? prop.PropertyType);             foreach (T item in data)             {                 DataRow row = table.NewRow();                 foreach (PropertyDescriptor prop in properties)                ...
Read more

Difference Between Site Template and Site Definition

Difference Between Site Template and Site Definition Before going into direct comparison, let me define both: Site Templates  : Are  snapshots of  sites at a point in time. When a user customizes a site from the UI or SPD, the custom template consists of the difference between the original state of the site (determined by its definition) and the state of the site or list when the custom template is generated. Custom templates remain tied to a particular site definition (for example, the site definition for SharePoint Web sites or Meeting Workspace Web sites), so that if the site definition is not present or is changed, the custom template cannot work. Site Definitions  : As the name implies, A Site definition is "core definition of a site”. Each site definition emerges through a combination of files that are placed in the 12 hive of WFE during installation of SharePoint. Site definition files include .xml, .aspx, .ascx, and .master page files, as well as docum...
Read more