Home Dashboard Directory Help
Search

The primary reference could not be resolved because it has an indirect dependency on the framework assembly which could not be resolved by Nigel Price


Status: 

Closed
 as Fixed Help for as Fixed


2
0
Sign in
to vote
Type: Bug
ID: 507919
Opened: 11/3/2009 10:49:52 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

I get the following warning message when I compile a solution which contains 10 projects :-
The primary reference "Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, processorArchitecture=AMD64" could not be resolved because it has an indirect dependency on the framework assembly "System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v3.5". To resolve this problem, either remove the reference "Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, processorArchitecture=AMD64" or retarget your application to a framework version which contains "System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35".

System.Web.DataVisualization 3.5.0.0 is loaded into the GAC. The result is that I get an error :-

The type or namespace name 'Office' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)

and the comp[ilation fails.


Details
Sign in to post a comment.
Posted by Jørn Cornelius Olsen on 2/5/2013 at 3:37 AM
I can reproduce the problem in Visual Studio 2012 version 11.0.51106.01 Update 1. The problem goes away when you install the "Microsoft Chart Controls for Microsoft .NET Framework 3.5".
Posted by chandrashekar kollipara on 9/4/2012 at 7:24 AM
We are using Visual studio 2010 version 10.0.40219.1 SPRel and still see the issue
Posted by alizproarts on 6/3/2011 at 4:31 AM
I resolved it by installing "Microsoft Chart Controls for Microsoft .NET Framework 3.5"
Posted by allyson.kreft on 6/3/2010 at 7:52 AM
What version contains the fix? I am using Version 10.0.30319.1 RTMRel and seeing this issue.
Posted by Microsoft on 1/6/2010 at 4:15 PM
This issue has been addressed in more current builds.
Posted by Nigel Price on 11/13/2009 at 3:29 PM
Hi Sean

The project has already been uploaded to https://sftus.one.microsoft.com/choosetransfer.aspx?key=29d17dec-bb58-49a7-a737-21af6d615967.

If you cannot get hold of this - please give me a workspace and I will upload the project for you.

Regards

Nigel
Posted by Microsoft on 11/13/2009 at 2:53 PM
Thank you reporting this issue. Please provide the project so we can repro. We do believe we have a similar bug that we are working on right now. If we can get your project we will be able to confirm that.

Thanks,
Sean
Posted by Microsoft on 11/8/2009 at 11:56 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you
Posted by Nigel Price on 11/6/2009 at 6:15 AM
I ahve uploaded the files as requested.

Regards

Nigel
Posted by Microsoft on 11/5/2009 at 10:23 PM
Thanks for reporting this issue.

In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Please provide us with a demo zipped project file so that we can conduct further research.

I have created a Workspace for you. Please upload file to it.

https://sftus.one.microsoft.com/choosetransfer.aspx?key=29d17dec-bb58-49a7-a737-21af6d615967

Password is 4ndfNV4Y!lTw20z

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.

Visual Studio Product Team
Posted by Microsoft on 11/4/2009 at 2:42 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.