Work around #1675 for C++ Code Analysis scenarios #1699
Conversation
This addresses the repro case for dotnet#1675, but not its root cause. By providing a `codeBase` for the CA assemblies, we ensure that any running MSBuild can find them when deserializing a log message.
|
@mavasani As discussed over email. I was a bit confused about what assemblies to involve here. I first tried with just |
|
@rainersigwald - that seems correct. FXCopTask assembly can be invoked from MSBuild and has a dependency on CodeAnalysis SDK. |
|
One other thing--the plan for dev15 is that those assemblies are only ever serviced in-place in the VS folder, right? They won't ever be loaded from a NuGet package or something? This would break that. |
|
Yes, these assemblies are not published via NuGet packages, they ship in the box. |
These assemblies have moved and versioned in dev16. Update of the workaround for dotnet#1675 in dotnet#1699.
This addresses the repro case for #1675, but not its root cause. By
providing a
codeBasefor the CA assemblies, we ensure that any runningMSBuild can find them when deserializing a log message.