Issues in WSP solutions with web application scoped resources in SharePoint 2010 mode

Question

I am working on migration from SharePoint 2010 to SharePoint 2013. I have mounted the content database in SharePoint 2013 and also deployed the WSPs from SharePoint 2010 which were created in Visual Studio 2010 to SharePoint 2013. Currently the site is running in SP 2010 mode.

The WSP solutions contain web application scoped resources and hence are deployed to web applications and not globally. There are SafeControl entries in the package, web parts, user control etc. Now when I browse the pages which contain the webparts I get the error:

Could not load type 'assemblyname'.

I have checked that all the physical files are deployed correctly to 14 hive, the dlls are all present in C:\Windows\assembly and the SafeControl entries are also present in web.config file. In the past I have had WSPs which deployed globally and I have not found any issues in them. There is a similar question over here:

"Could not load type" from custom SharePoint 2010 WSP deployed to SharePoint 2013

UPDATE

I created few simple VisualWebPart projects in VS 2010, deployed them to a web application in SP 2010 and then migrated the application to SP 2013 and deployed the solutions there. Everything works fine. That means this issue is not specific to web application scoped SharePoint solutions which I originally thought. There is something else going on in my projects which I am not able to identify.

Answer 1

i dont exactly know how it works in2010 with the wsp but i would of thought that the initial wsp can be converted which is fine as it uses .net 3.5

the issue is your getting the error:

Could not load type 'assemblyname'.

this tells me that there is a reference that is not referenced! so in your project within vs you need to upgrade custom dlls that are referenced for 2010 to 2013!

as noted:

Visual Studio 2012 -> Create new solution -> Under SharePoint 2013 select "Import SharePoint 2010 Solution

that should solve the issue.. but as you are looking for it to work off the bat i would presume that a dll within the project under reference is not set properly or doesnt exist in 2013 to work but it does in 2010!

have you tried a simple webpart like hello world? click a button and it shows hello world on a lable? see if it works which it should. Im still going with the fact that there is a dll in your project that doesnt exist in 2013 (assemble for 2010 3.5) and not assembly 4.0!

EDIT

ok this is worth a try:

try putting the dll that is causing the issue within the web application dll folder!

C:\inetpub\wwwroot\wss\VirtualDirectories\youwebappFolder\bin

that should do the trick ;)

just to make it clear that the error your getting is Could not load type 'assemblyname'. ? so there is somthing called assemblyname in your project? or have you just renamed it?

if the issue still persists than you need to force compile on the .cs class that you have named 'assemblyname'. within vs2012 goto the .cs class in question -> properties -> change build action to compile! build and deploy, the 'assemblyname' should now work as its compiled properly within the dll and packaged properly within the wsp!

Answer 2

I am assuming - you are not facing with WSPs which are Globally deployed. Only with Web Application scoped

Can you retract the solution and check if it is 100% removed from GAC and 14 hive. Try IIS and try to deploy one more time