Skip to content
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

PlatformSpecificAnalyzer does not suggest any fixes #3282

Closed

Description

@MartinZikmund

Describe the bug

I am not able to get any suggestions from Platform Specific analyzer. My app targeting 18362 uses ThemeShadow, which is not available in earlier versions. My min version is set to 16299, but Analyzer does not show any suggestions that the code will not actually work there. Is there some step I am missing (except for installing the analyzer NuGet package?)

Visual Studio version info is listed below.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Create UWP project targeting 18362 with min version 16299
  2. Install analyzer NuGet package
  3. Use ThemeShadow in code
  4. Observe there is no suggestion to make code version adaptive

Expected behavior

Analyzer should underline the problematic code.

NuGet Package(s):

Package Version(s):

Windows 10 Build Number:

  • Fall Creators Update (16299)
  • April 2018 Update (17134)
  • October 2018 Update (17763)
  • May 2019 Update (18362)
  • Insider Build (build number: )

App min and target version:

  • Fall Creators Update (16299)
  • April 2018 Update (17134)
  • October 2018 Update (17763)
  • May 2019 Update (18362)
  • Insider Build (xxxxx)

Device form factor:

  • Desktop
  • Xbox
  • Surface Hub
  • IoT

Visual Studio

Microsoft Visual Studio Enterprise 2019
Version 16.5.4
VisualStudio.16.Release/16.5.4+30011.22
Microsoft .NET Framework
Version 4.8.03752

Additional context

Add any other context about the problem here.

Activity

  1. added
    bug 🐛An unexpected issue that highlights incorrect behavior
    on May 13, 2020
  2. michael-hawker commented on May 14, 2020

    @michael-hawker
    Member

    Hey @MartinZikmund thanks for filing an issue, this is a known one though: #2999

    When the analyzers were originally added, they were just comparing between a couple of versions, so they've been a bit harder to adapt to handling versions since apparently.

    Any suggestions or input on that conversation would be most welcome, thanks!

  3. michael-hawker commented on Jul 22, 2020

    @michael-hawker
    Member

    Unfortunately going to close this issue, we just don't have the data to make the analyzers work, see #3396. Please follow-up with the need for this in the discussion on CsWinRT here.

  4. ghost locked as resolved and limited conversation to collaborators on Sep 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions