chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
0 votes
Hi, unlike most other assemblies that are referenced by a Visual Studio project from the GAC, TypeMock adds a <HintPath> tag to the project references, e.g. -

for nunit -
<Reference Include="nunit.framework, Version=2.4.0.2, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77, processorArchitecture=MSIL" />

but for TypeMock -
<Reference Include="TypeMock, Version=3.7.1.0, Culture=neutral, PublicKeyToken=3dae460033b8d8e2">
<SpecificVersion>False</SpecificVersion>
<HintPath>........Program FilesTypeMockTypeMock.NETTypeMock.dll</HintPath>
</Reference>

If the project is then moved to another location on the same drive, the reference will be broken. Why does TypeMock not work the same as other applications, or at least write an absolute <HintPath>?
(actually, if the project is on another drive, TypeMock does write a absolute <HintPath>)

Thanks, John.
asked by JohnAr (600 points)

1 Answer

0 votes
Hi John
It seems to me like it's connected to the visual studio behavior.
We didn't do anything to get this behavior.
I will check to see if there is a way that we can modify the HintPath property.
answered by ohad (35.4k points)
...