they are the dll's used by visual studio itself. visual studio updates update as needed.
Microsoft DLLS in C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\PublicAssemblies
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 41%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Moore, Ronald
1
Reputation point
I'm using Microsoft Visual studio 2022 version 17.14.13
I noticed that the directory C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\PublicAssemblies
contains dlls such as Microsoft.Bcl.AsyncInterfaces.dll
But this directory contains versions that are different from the ones I get from nuget.
They seem to be preview versions
How can I update the dlls that are present in this directory with the versions I pull from nuget
Developer technologies | C#
2 answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Bruce (SqlWork.com) 79,526 Reputation points Volunteer Moderator2025-08-27T15:57:28.2133333+00:00 -
Moore, Ronald 1 Reputation point
2025-08-27T16:06:44.3766667+00:00 Yes but MSBUILD is using this file [Microsoft.Bcl.AsyncInterfaces.dll] sourced from
Copying file from "c:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\PublicAssemblies\Microsoft.Bcl.AsyncInterfaces.dll" to "C:\GUI\bin\Debug\Microsoft.Bcl.AsyncInterfaces.dll".
This file is implicitly being added to my bin folder and its the wrong version. How do I fix that
-
Moore, Ronald 1 Reputation point
2025-08-27T17:54:11.71+00:00 I have 2 projects in my solution
Project A explicitly references \packages\Microsoft.Bcl.AsyncInterfaces.1.1.0\lib\net461\Microsoft.Bcl.AsyncInterfaces.dll
Project B doesn't explicitly references Microsoft.Bcl.AsyncInterfaces.dll
MSBUILD is making Project B
use c:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\PublicAssemblies\Microsoft.Bcl.AsyncInterfaces.dll" to "C:\GUI\bin\Debug\Microsoft.Bcl.AsyncInterfaces.dll
I don't want Project B to include Microsoft.Bcl.AsyncInterfaces.dll at all.
How do I accomplish that?
-
Moore, Ronald 1 Reputation point
2025-08-27T18:15:25.29+00:00 I have 2 projects in my solution
Project A explicitly references \packages\Microsoft.Bcl.AsyncInterfaces.1.1.0\lib\net461\Microsoft.Bcl.AsyncInterfaces.dll
Project B doesn't explicitly references Microsoft.Bcl.AsyncInterfaces.dll
MSBUILD is making Project B
use c:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\PublicAssemblies\Microsoft.Bcl.AsyncInterfaces.dll" to "C:\GUI\bin\Debug\Microsoft.Bcl.AsyncInterfaces.dll
I don't want Project B to include Microsoft.Bcl.AsyncInterfaces.dll at all.
How do I accomplish that?
-
Bruce (SqlWork.com) 79,526 Reputation points Volunteer Moderator
2025-08-27T20:16:22.2066667+00:00 best practice would be to use nuget packages, say Microsoft.Bcl.AsyncInterfaces so you control the dependencies.
typically project templates, nuget packages or canned folders contain the oldest possible version, so as not to cause compatibility issues (work with largest possible set of versions). for example if they included the latest Microsoft.Bcl.AsyncInterfaces, but you added a dependency that did not support that version version yet, the build would fail, and the solution might be complex.
it better if you control the actual nuget versions in the file assembly.
note: you have the same issue with nuget transient dependencies
-
Moore, Ronald 1 Reputation point
2025-08-27T20:48:40.6666667+00:00 What if I have a project A that references Project B
Project A doesn't explicitly use Microsoft.Bcl.AsyncInterface
Project B explicitly use Microsoft.Bcl.AsyncInterface via nuget
When I build Project A c:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\PublicAssemblies\Microsoft.Bcl.AsyncInterfaces.dll" to "C:\GUI\bin\Debug\Microsoft.Bcl.AsyncInterfaces.dll is used
instead of the Microsoft.Bcl.AsyncInterfaces.dll from nuget.
How do I fix that?
-
Bruce (SqlWork.com) 79,526 Reputation points Volunteer Moderator
2025-08-27T20:58:07.63+00:00 as project A doesn't reference Microsoft.Bcl.AsyncInterface, and project B references via nuget, its a nuget transient dependency and the version will be the one specified in project A.
if you want project A to control the version, add a nuget reference to project A. you would need to do this if project A used a nuget package that referenced Microsoft.Bcl.AsyncInterface (which typically would not be the current version) and you wanted to use the latest (say from a nuget security warning).
note: nuget package references are not updated just because of security alerts, only if a breaking change requires a newer version.
-
Moore, Ronald 1 Reputation point
2025-08-27T21:13:39.8366667+00:00 Since Project A Doesn't explicitly reference Microsoft.Bcl.AsyncInterface, how do I know which version its going to use.
Sign in to comment -
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more