You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm playing with Roslyn and wanted to create my first analyzer. It works fine, however, when I try to update NuGet packages in analyzer project I get an error because analyzer is supporting .net4.5 only while Microsoft.CodeAnalysis.Common 2.* doesn't. When I tried to migrate project manually to .net4.6 or .netstandard I encountered with several problems because I don't understand all switches and custom project sections in generated project and I only get multiple errors, and when I fix ones others comes. Here is #44 and #510 that are helpful in implementing it and it's a step in the same direction. I think that new Update Analyzer with Code Fix template must be a .netstandard project referencing packages 2.*.
P.S. If here is a workaround how to perform such a transformation manually after project got generated it would be really helpful.
From @Pzixel on July 18, 2017 9:16
I'm playing with Roslyn and wanted to create my first analyzer. It works fine, however, when I try to update NuGet packages in analyzer project I get an error because analyzer is supporting .net4.5 only while
Microsoft.CodeAnalysis.Common
2.* doesn't. When I tried to migrate project manually to .net4.6 or .netstandard I encountered with several problems because I don't understand all switches and custom project sections in generated project and I only get multiple errors, and when I fix ones others comes. Here is #44 and #510 that are helpful in implementing it and it's a step in the same direction. I think that newUpdate Analyzer with Code Fix
template must be a .netstandard project referencing packages 2.*.P.S. If here is a workaround how to perform such a transformation manually after project got generated it would be really helpful.
Copied from original issue: dotnet/sdk#1424
The text was updated successfully, but these errors were encountered: