For the extension to work, you need to specify a configuration file that essentially only contains paths (one per line) for searching for projects:
When you click the
Project dependency search is based on
If the file is present, then the extension starts processing explicit and implicit (transitive) dependencies of the project - NuGet packages, framework assemblies. After processing, the Messages tab of the Error List displays information about each changed project and the references included in it.
When working with references, only evaluated items are used. In this example, when using the Debug configuration, reference A will be replaced, while for the Release configuration, reference B.
Multitargeting as such does not have special support, i.e. a project with
Will be processed as if it had
Separate lines entered in the configuration file can be commented out as follows:
With this configuration, at the moment of switching references, the search will be performed only in the last two directories.
It is assumed that in the stable version the extension should support Visual Studio 17, 19. However, at the moment, such compatibility is not guaranteed like anything else. The author conducted an initial test in the next version of Visual Studio:
.NET SDK version >= 3.0 is required since version 0.5.0.