<HintPath> in *.csproj file doesn't work for VS2012. - by SoBigSoBig

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<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 758647 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 8/18/2012 8:59:19 PM
Access Restriction Public


The following CodedUI Dlls are shipped with VS2012. What I did was just copy them to a separate folder and reference them from there. I checked the *.csproj file, it has the correct <HintPath> info as below. But in VS2012 property window, I checked the reference path, they are STILL resolved the default locations like "D:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ReferenceAssemblies\v4.0\Microsoft.VisualStudio.QualityTools.CodedUITestFramework.dll"

The <HitPath> works for only one of the following DLLs, the "Microsoft.VisualStudio.QualityTools.UnitTestFramework". But I don't see anything different between how this DLL is referenced and the others.

Why is this happening?

I see some other guy reported a bug about VS 2012 assembly binding.(http://social.msdn.microsoft.com/Forums/en/vsunittest/thread/ba271f86-ed33-49a5-9b52-99980e88d198)

But I am using the RTM version! This is blocking our whole project!!

    <Reference Include="Microsoft.VisualStudio.QualityTools.CodedUITestFramework, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL">
     <Reference Include="Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL">
     <Reference Include="Microsoft.VisualStudio.TestTools.UITest.Common, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL">
     <Reference Include="Microsoft.VisualStudio.TestTools.UITest.Extension, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL">
     <Reference Include="Microsoft.VisualStudio.TestTools.UITesting, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL">
Sign in to post a comment.
Posted by Ion [MSFT] on 10/9/2012 at 8:22 PM
Hi, please reference to this ConnectId for more information 758629.
Posted by Ion [MSFT] on 8/22/2012 at 1:50 PM
Hi, we have identified the nature of the issue and we are tracking it with another connect bug. We will update you once we have more information. Thanks
Posted by Ion [MSFT] on 8/21/2012 at 8:00 PM

I was not able to repro this bug, I copied the 5 assemblies to a private directory, then I added a reference to the assemblies using Browse in the RM dialog. They are resolved from the private directory. In the project file they also have a HintPath.

Is there some additional steps you are doing? What type of project and fx version are you targeting?

This might also be a transient display issue, you can also check the resolution path by setting the build verbosity to "Detailed" in Tools - Options - Projects and Solutions - Build and Run - MSBuild project build output verbosity. Do a build or rebuild, then in the Output Window look for the "ResolveAssemblyReference" task, you should see entries like "Primary reference "Microsoft.VisualStudio.QualityTools.CodedUITestFramework... Resolved file path is ...". Can you confirm the resolved path logged is also icorrect?
Posted by Macy [MSFT] on 8/19/2012 at 8:07 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.
Posted by Helen [MSFT] on 8/18/2012 at 9:54 PM
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)