.NET Framework 4.0 assemblies cannot use .NET Framework 3.5 assemblies - by AlexDemche

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 510563 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 11/14/2009 8:16:41 AM
Access Restriction Public


1. Convert solution of VS 2008 to VS 2010 solution. VS 2008 solution projects has target framework - 3.5
2. Create new project at converted solution using VS 2010
3. Add project or dll reference to any older (converted) project with Target Framework 3.5
4. Compile solution or new project

Get error:
Error	3	The type or namespace name 'NAME_OF_OLDER_PROJECT' could not be found (are you missing a using directive or an assembly reference?)	C:\Users\1\Documents\Visual Studio 2010\Projects\SEOTools_svn\MyNewProject\Program.cs	5	7
Sign in to post a comment.
Posted by AaronHoffman on 2/2/2010 at 8:34 AM
I was able to reproduce this issue with the steps that were provided. I think the root of the issue is that a project that is targeting the 4.0 framework is referencing a project targeting the 3.5 framework.

I'm not sure that this is a bug - it is probably by design.
Posted by Microsoft on 11/19/2009 at 9:18 PM
Hi, given that we have not heard back from you in 7 days, we will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 11/16/2009 at 1:21 AM
Thanks for reporting the 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.

Could you please attach a zipped project file to help us reproduce the issue?

Thanks again for your efforts and we look forward to hearing from you.
Visual Studio Product Team