You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/msbuild/troubleshoot-assembly-references.md
+23-1Lines changed: 23 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,29 @@ There were recent fixes made to `ResolveAssemblyReference` to alleviate the situ
150
150
151
151
There are two ways to customize the list of paths `ResolveAssemblyReference` searches in attempting to locate an assembly. To fully customize the list, the property `AssemblySearchPaths` can be set ahead of time. The order matters; if an assembly is in two locations, `ResolveAssemblyReference` stops after it finds it at the first location.
152
152
153
-
By default, there are ten locations `ResolveAssemblyReference` searches (four if you use the .NET SDK), and each can be disabled by setting the relevant flag to false:
153
+
`AssemblySearchPaths` is a semicolon-delimited list. It supports a set of built-in placeholders (for example, `{HintPathFromItem}` and `{GAC}`) that expand to actual locations during resolution.
154
+
155
+
By default, non-SDK-style projects use the following search path order:
0 commit comments