• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1525
  • Last Modified:

Can't resolve project reference because of indirect dependency on current target framework (I think!)

Can someone please translate this into English?
The primary reference
"Microsoft.SQLServer.ManagedDTS, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=MSIL"
could not be resolved because it has an indirect dependency on the .NET Framework assembly
"mscorlib, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
which has a higher version "2.0.3600.0"
than the version "" in the current target framework.
Is this a problem with the target version of MY PROJECT or a problem between .Net and the SQL Server library I'm trying to use?

I need to target .Net 2.0, but I don't care what sub-level (2.0.3600).  Can this be changed?  I looked under project properties and didn't see anyway to change the sub-level (only between .Net 2, 3.5, 4, etc.)

What do I need to do to get around this?
1 Solution
Carl TawnSystems and Integration DeveloperCommented:
It appears to be an issue with SQL 2005 using a pre-release version of the XML6 dll which has a higher version number than the final release.

This article explains the issue in detail and includes details on how to fix it:

ZuZuPetalsAuthor Commented:
That's a good article--thanks!

I solved the problem by upgrading all projects from .Net 2 to .Net 4.
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.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now