SSRS Unable to deploy project with custom assembly to SQL 2012

Using Visual Studio 2013 with BI I created a SSRS project which I have been successfully deploying for months.  This week I created a customer assembly DLL and referenced it in all the project's reports.  While this works on my development machine I am unable to deploy it to my SQL Server 2012 server with the following error:


Error rsProcessingError : Error while loading code module: ‘DSSFunctions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’.
Details: Could not load file or assembly 'DSSFunctions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies.
This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

I believe this is down to the referenced Microsoft.ReportingServices.ProcessingObjectModel.  This is version 12 on my development machine but is 11 on the server.
canuckconsultingAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Walter PadrónCommented:
The .Net framework on the server is older than the framework on your developer machine.
You can install a newer version on the server or set the project that build the custom DLL to target an older framework version.

Best regards
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
canuckconsultingAuthor Commented:
That doesn't appear to be the case here.  I took screenshots of the relevant registry entries and the framework match at 4.5.1  as per the definitions below:

.Net Framework Versions
Server .Net version
Development .Net version
I also ran CLRVER.EXE on both systems showing they have the same versions:

CLRVER Results Side by SideI really think it's that ProcessingObjectModel but can't work out how to get to the next step.
0
canuckconsultingAuthor Commented:
Turned out to be related to .Net version with the issue being SSRS itself was built using .Net 3.5 and .20.  I rebuilt my project to .Net 3.5 and worked.

For me another issue was the version of Microsoft.ReportingServices.ProcessingObjectModel which I required to be able to pass parameters from my report to the custom assembly.  On my development machine my custom assembly is built using version 12 of the DLL.  However when deploying to SQL 2012 I need to use a version of the assembly instead referencing version 11 which I copied rom the target machine.  This is a bit messy for now but at least it works.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SSRS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.