Visual Studio 2012 - Add Fakes Assembly does not add all needed references - by T.M. Douma

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


4
0
Sign in
to vote
ID 782031 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 3/25/2013 7:07:49 AM
Access Restriction Public

Description

In one of our projects  Visual Studio 2012's  option "Add Fakes Assembly" does not add all needed references to the generated f.csproj file.

This is causing an error.

Error	1	The type '<typename>' is defined in an assembly that is not referenced. You must add a reference to assembly '<ReferencedAssembly>, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6740fce60587153a'. [C:\Projects\TFS\<TestProject>\obj\Release\Fakes\dfzab\f.csproj]	C:\Projects\TFS\<TestProject>\f.cs	31599	26	<ProjectName>


The Assembly I'm generating the fake for does have a reference to correct assembly.

After examing the f.csproj file i noticed the reference to the assembly was not there.

I managed to reproduce this issue in a Demo Project. I added the project to this feedbackitem.
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:29 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 5/15/2013 at 3:37 PM
T.M. Douma,

I just fixed this bug and I also tried your attached project. The generated F.CSPROJ now compiles fine. It should be available in the later release.

Thanks!
Patrick Tseng
Posted by Microsoft on 4/25/2013 at 9:11 AM
T.M. Douma,

Thanks for reporting this issue to us. The product team is currently investigating the proper fix and timing to address this issue.

Thanks,
Joshua Weber
Posted by Microsoft on 3/26/2013 at 1:31 AM
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.
Posted by Microsoft on 3/25/2013 at 9:32 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 3/25/2013 at 7:51 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)