| Reporter |
Tristen Fielding (kaboo)
|
|---|---|
| Created | Feb 17, 2012 12:56:33 AM |
| Updated | Feb 18, 2012 12:09:42 AM |
| Priority | Normal |
| Type | Bug |
| Fix versions | No Fix versions |
| State | Submitted |
| Assignee | Unassigned |
| Subsystem | Language - C# |
| Affected versions | 6.0 |
| Fixed in build | No Fixed in build |
We have conditional reference due to C++ DLL naming conventions, in our .csproj files we have code like this:
<Reference Include="System.Data" />
<Reference Include="System.Xml" />
<ItemGroup Condition=" '$(Configuration)' == 'NightBuild Release' ">
<Reference Include="TsShare.Net">
<HintPath>..\..\..\..\bin\TsShare.Net.dll</HintPath>
</Reference>
</ItemGroup>
<ItemGroup Condition=" '$(Configuration)' == 'Debug' ">
<Reference Include="TsShare.Net">
<HintPath>..\..\..\..\bin\TsShare.Netd.dll</HintPath>
</Reference>
</ItemGroup>
However, at times, Resharper detects both and complains about ambiguities. We have seen this issue if both version of the dll are available. Or deleted and recreated during a re-build process. To resolve this issue we must unload the project and reload, which is impractical when you have 30+ projects.
<Reference Include="System.Data" />
<Reference Include="System.Xml" />
<ItemGroup Condition=" '$(Configuration)' == 'NightBuild Release' ">
<Reference Include="TsShare.Net">
<HintPath>..\..\..\..\bin\TsShare.Net.dll</HintPath>
</Reference>
</ItemGroup>
<ItemGroup Condition=" '$(Configuration)' == 'Debug' ">
<Reference Include="TsShare.Net">
<HintPath>..\..\..\..\bin\TsShare.Netd.dll</HintPath>
</Reference>
</ItemGroup>
However, at times, Resharper detects both and complains about ambiguities. We have seen this issue if both version of the dll are available. Or deleted and recreated during a re-build process. To resolve this issue we must unload the project and reload, which is impractical when you have 30+ projects.