{ThemeResource} IntelliSense is not working

[MartinZikmund]

Current behavior

It appears that in some update of Visual Studio the IntelliSense support for {ThemeResource} and {StaticResource} stopped working, even if -windows10.0.xyz is selected as the target:

Expected behavior

Should work

How to reproduce it (as minimally and precisely as possible)

No response

Workaround

No response

Works on UWP/WinUI

Yes

Environment

No response

NuGet package version(s)

No response

Affected platforms

No response

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

[DevTKSS]

bit curous about sometimes it is actually appearing, but not everytime and not the Keys defined in the uno ResourceDictionary found in the templated app:


for reference added my namspace imports

[DevTKSS]

Hurray re-found this issue😁 would like to link this, handling same issue, please check which ob issue destinations are the better one.
unoplatform/Uno.Themes#1503

@MartinZikmund
The issue source seems to be that the themes I actually get are coming from a generic resources file only found in WindowsAppSDK which is only included in windows target packages.
Idea to solve it would be Plattform specific # in the app.xaml that is adding a package/file reference for the other platforms like if material is used we could maybe add a ref to the resources coming from this?
Also if you take a look into the listed theme Ressource keys I am getting, they are kind of useless to me because my application is in this case using material and i get only intellisense for the windows fluent keys😅
I think that is a really classic usecase for when to use Plattform specific # 🙃

[DevTKSS]

Ah and to be added, i tryed this with latest updates of visual studio community edition and latest version of uno.sdk (5.5.56) created project via vs 2022 uno wizard and uno-check did update all used project templates to latest version.

[MartinZikmund]

@DevTKSS technically the intellisense should just work for Material resources as it is referenced in App.xaml - especially for WinAppSDK target it should just work out of the box