Currently the project template places analyzers and code fixes in the same assembly. This results in a dependency on Microsoft.CodeAnalysis.Workspaces which is easy to accidentally use in an analyzer, resulting in type load exceptions when building from the command line. For example, DotNetAnalyzers/StyleCopAnalyzers#1352 was the underlying cause of DotNetAnalyzers/StyleCopAnalyzers#1659, which was extremely difficult to track down but would have been easily avoided if the assemblies were separated from the start.
Currently the project template places analyzers and code fixes in the same assembly. This results in a dependency on Microsoft.CodeAnalysis.Workspaces which is easy to accidentally use in an analyzer, resulting in type load exceptions when building from the command line. For example, DotNetAnalyzers/StyleCopAnalyzers#1352 was the underlying cause of DotNetAnalyzers/StyleCopAnalyzers#1659, which was extremely difficult to track down but would have been easily avoided if the assemblies were separated from the start.