Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7526259
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 30, 20262026-05-30T03:46:57+00:00 2026-05-30T03:46:57+00:00

I have 3 assemblies, a WP7 app (targeting 7.0), a Web Services project (running

  • 0

I have 3 assemblies, a WP7 app (targeting 7.0), a Web Services project (running 4.0), and a Portable Class Library (built from the template & targeting WP7, SL4 & .NET 4.0) which contains a common type used between the first two.

When run locally (in IIS Express) things work just fine, however when run against a deployed instance of the Web Services assembly (on a remote IIS server I have little control of) fails with the following exception:

System.IO.FileNotFoundException: Could not load file or assembly
‘System.Xml.Serialization, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089’ or one of its dependencies. The
system cannot find the file specified. File name:
‘System.Xml.Serialization, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089’ —> System.IO.FileNotFoundException:
Could not load file or assembly ‘System.Xml.Serialization,
Version=2.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35,
Retargetable=Yes’ or one of its dependencies. The system cannot find
the file specified. File name: ‘System.Xml.Serialization,
Version=2.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35,
Retargetable=Yes’

The stacktrace indicates that it is on the first call into the PCL, which would make sense if it’s a type load failure like above.

If I remove the reference to the PCL assembly and then add the key class file to both assemblies, things work fine, however I want to avoid this kind of code duplication… so the question is: Why is this happening? How can I configure the PCL to function as written?

EDIT: A little more information… my PCL uses XmlSerializer, something that lives in System.Xml.dll on the desktop, and in System.Xml.Serialization.xml in Silverlight… an assembly that doesn’t exist under the full desktop framework… so this failure makes some sense, only in the PCL world, some of these assemblies/classes are broken out on their own

In this case, XmlSerializer actually lives in C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETPortable\v4.0\Profile\Profile2\System.Xml.Serialization.dll (which is referenced by the PCL)… as a test I added the same reference to the Web Project… however at runtime of the web project, it fails with yellow screen of death stating that:

Could not load file or assembly ‘System.Xml.Serialization’ or one of
its dependencies. The located assembly’s manifest definition does not
match the assembly reference. (Exception from HRESULT: 0x80131040)

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-30T03:46:58+00:00Added an answer on May 30, 2026 at 3:46 am

    You will need to install KB2468871 on the remote server. It’s a GDR that has been pushed to most client machines – however, servers will need to opt into it (they typically don’t automatically install updates).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm having a problem with assembly references. I have four assemblies: A class library
I have several assemblies my project is dependant upon. These are stored in the
I have an Azure webrole in my VS project. I have assemblies in my
Say you have two assemblies (two dlls). The first contains a class called Base
I have an app built against MVC Preview 3 (referencing local copies of the
Given the following setup, I have three assemblies. Web (ASP.NET MVC 3.0 RC1) Models
Let's say I have two assemblies: BusinessLogic and Web. BusinessLogic has an application setting
We have many assemblies ( class libraries ) which our main application uses. I
I have a WP7 app that I recently upgraded to WP7.1 (including the MVVM-Lite
I have 2 assemblies, A containing the Main method and the Foo class, that

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.