So, there is now a convention for where to put analyzers in a NuGet package, and it's important to follow this convention if you want them to work properly with anything other than the old packages.config format, since that's the only situation in which install.ps1 and uninstall.ps1 will ever run: neither Paket nor NuGet v3 in project.json mode will pick up analyzers that aren't located according to the convention.
The convention is basically to put analyzers in an analyzers/dotnet directory within their package, and to further split any language-specific analyzer DLLs into cs and vb subdirectories under that. (Or you could follow the links above for the details, most of which are fairly irrelevant so far.)
Btw, this concerns the packages:
- Microsoft.VisualStudio.ProjectSystem.Analyzers (14.0.50729-pre)
- Microsoft.VisualStudio.Threading.Analyzers (14.1.114-pre)
(Not sure the latter is strictly-speaking yours, but the package doesn't exactly point at a bug tracker and your "Project Type" template pulls it in, so I might as well list it while I'm here ...)
So, there is now a convention for where to put analyzers in a NuGet package, and it's important to follow this convention if you want them to work properly with anything other than the old
packages.configformat, since that's the only situation in whichinstall.ps1anduninstall.ps1will ever run: neither Paket nor NuGet v3 inproject.jsonmode will pick up analyzers that aren't located according to the convention.The convention is basically to put analyzers in an
analyzers/dotnetdirectory within their package, and to further split any language-specific analyzer DLLs intocsandvbsubdirectories under that. (Or you could follow the links above for the details, most of which are fairly irrelevant so far.)Btw, this concerns the packages:
(Not sure the latter is strictly-speaking yours, but the package doesn't exactly point at a bug tracker and your "Project Type" template pulls it in, so I might as well list it while I'm here ...)