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
Expected Behavior: The call to function returns 1 diagnostic
Actual Behavior: The call to function returns 0 diagnostic, even though the analyzer does run an does create the diagnostic
BUT Adding TFM = net6-windowsXXX and Sdk="Microsoft.NET.Sdk" to the UWP project csproj (although invalid for UWP) fixes the issue where it returns the correct diagnostics that are reported.
This is happening at this line of the .NET Upgrade Assistant Project. Running our analyzers on a UWP project gives 0 diagnostic results while running this on a Net6 project gives the correct expected results.
The text was updated successfully, but these errors were encountered:
Version Used: Microsoft.CodeAnalysis.Analyzers 3.3.2
Steps to Reproduce:
Expected Behavior: The call to function returns 1 diagnostic
Actual Behavior: The call to function returns 0 diagnostic, even though the analyzer does run an does create the diagnostic
BUT Adding
TFM = net6-windowsXXX
andSdk="Microsoft.NET.Sdk"
to the UWP project csproj (although invalid for UWP) fixes the issue where it returns the correct diagnostics that are reported.This is happening at this line of the .NET Upgrade Assistant Project. Running our analyzers on a UWP project gives 0 diagnostic results while running this on a Net6 project gives the correct expected results.
The text was updated successfully, but these errors were encountered: