Getting "Cannot resolve symbol 'XXXXXX'" error after upgrading from WinUI3 to Project Reunion 0.8 stable version

microsoft / WindowsAppSDK

The Windows App SDK empowers all Windows desktop apps with modern Windows UI, APIs, and platform features, including back-compat support, shipped via NuGet.

https://docs.microsoft.com/windows/apps/windows-app-sdk/

MIT License

3.73k stars 309 forks source link

Getting "Cannot resolve symbol 'XXXXXX'" error after upgrading from WinUI3 to Project Reunion 0.8 stable version #1032

Open abhi-msft opened 3 years ago

abhi-msft commented 3 years ago

I recently upgraded my WinUI3 desktop app to Project Reunion 0.8 version using the upgrade instructions. When I open any XAML file, I am getting "Cannot resolve symbol 'XXXXXX'" suggestions/warnings. All these are related to Microsoft.UI.XAML namespace. However, the app builds and runs fine. I tried repro on a new app using the template and it does not have this issue. Seems like some missing links between Project-Reunion package and how Microsoft.UI.XAML is packaged into it, not sure. Am I missing anything?

Steps to reproduce the bug Take an existing WinUI3 app and upgrade it to Project Reunion 0.8 either directly or to 0.5 and then 0.8.

Expected behavior XAML should resolve without any issues.

Screenshots

Version Info Project-Reunion: 0.8 OS Build: 19042

MikeHillberg commented 3 years ago

@abhi-msft, what version of Visual Studio are you using? Errors showing up in VS but not in build usually means something related to Intellisense is out of sync.

abhi-msft commented 3 years ago

Thought so, I am using VS 16.10.3.

MikeHillberg commented 3 years ago

I think that's the latest public release. @alwu-msft might have ideas?

abhi-msft commented 3 years ago

Yes, that's the latest public release. VS 16.11.0 Preview 2.0 version does not have this issue.

evelynwu-msft commented 3 years ago

How are you upgrading your project: VS's Nuget Package Manager, or in a text editor/nuget.exe and then opening the upgraded project in VS? Does this persist after restarting VS? My instinctive thought is that stale information is hanging around in VS's caches.

abhi-msft commented 3 years ago

Used VS Package Manager. Tried all I can think of restarting VS, deleting the packages folder under my user, and restarting the machine itself.

evelynwu-msft commented 3 years ago

Bizarre! Would you mind sharing the upgraded project? One final thought... maybe there's something stale left in bin/ or obj/?

abhi-msft commented 3 years ago

Oh yes, that's one more thing I did in my list of tries, Cleaned them as well 😁 but the same result 🙄 I will strip out few things and send you the project internally, would that be, OK?