Skip to content

Commit 14cc8f4

Browse files
Update broken link to RAR target in Microsoft.Common.CurrentVersion.targets (dotnet#5386)
* Update broken link * Update documentation/wiki/ResolveAssemblyReference.md Co-authored-by: Rainer Sigwald <[email protected]> Co-authored-by: Rainer Sigwald <[email protected]>
1 parent 93fec27 commit 14cc8f4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

documentation/wiki/ResolveAssemblyReference.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ If you notice the ordering, ResolveAssemblyReferences is happening before Compil
99

1010
## Source Code
1111
You can browse Microsoft's MSBuild targets online at:
12-
http://source.roslyn.io/#MSBuildFiles/C/ProgramFiles(x86)/MSBuild/14.0/bin_/amd64/Microsoft.Common.CurrentVersion.targets,1820
12+
https://github.com/microsoft/msbuild/blob/a936b97e30679dcea4d99c362efa6f732c9d3587/src/Tasks/Microsoft.Common.CurrentVersion.targets#L1991-L2140
1313
This is where the RAR task is invoked in the targets file.
1414

1515
The source code for RAR is at:
@@ -149,4 +149,4 @@ There were recent fixes made to RAR to alleviate the situation. You can control
149149

150150
A common situation is MSBuild gives a warning about different versions of the same assembly being used by different references. The solution often involves adding a binding redirect to the app.config file.
151151

152-
A useful way to investigate these conflicts is to search in MSBuild Structured Log Viewer for "There was a conflict". It will show you detailed information about which references needed which versions of the assembly in question.
152+
A useful way to investigate these conflicts is to search in MSBuild Structured Log Viewer for "There was a conflict". It will show you detailed information about which references needed which versions of the assembly in question.

0 commit comments

Comments
 (0)