Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

resource could not be resolved in WPF in VS2019 #2183

Closed
WeixiangZhang opened this issue Dec 3, 2020 · 5 comments
Closed

resource could not be resolved in WPF in VS2019 #2183

WeixiangZhang opened this issue Dec 3, 2020 · 5 comments
Labels
Waiting on feedback Additional information is needed. Stale items with this label may be closed.

Comments

@WeixiangZhang
Copy link

WeixiangZhang commented Dec 3, 2020

Version: MaterialDesignTheme 3.2 via Nuget
VS2019: v16.8.2

I setup project following Getting Started.
But the resources could not be resolved in designer, but it‘s ok when running.

And use VS2015 to open this VS2019 solution, the resources can be resolved in designer.

How to fix this? Thanks.

error

app

@SandnerSoft
Copy link

Hello,

same issue here.

@Keboo
Copy link
Member

Keboo commented Dec 7, 2020

A few follow up questions.

  1. MaterialDesignIconButton is an optional style, so you will need to explicitly reference the Buttons resource dictionary (example here). For more information on this see this wiki page.
  2. What version of Visual Studio are you using? You can find this from the Help >> About Microsoft Visual Studio menu at the top.
  3. What version of .NET is your app targeting (.NET Framework, .NET Core 3.1, .NET 5)?

@Keboo Keboo added the Waiting on feedback Additional information is needed. Stale items with this label may be closed. label Dec 7, 2020
@WeixiangZhang
Copy link
Author

@Keboo
I followed Quick Start to setup.
1

VS2019 info:
2

Net framework info:
3

@WeixiangZhang
Copy link
Author

@Keboo In my tests, this issue is caused by x64 platform.

In VS2019, set platform to x64 will cause this issue and even set back to Any CPU or x86, it will not recover.
Clean and rebuild resolution will not work.
4

But in VS2015, set back to Any CPU, it works and resources could be resolved.

So when use VS2019, I must be very careful not to set platform to x64......

@ElieTaillard
Copy link
Member

Is the issue solved ?

@ElieTaillard ElieTaillard closed this as not planned Won't fix, can't repro, duplicate, stale Aug 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Waiting on feedback Additional information is needed. Stale items with this label may be closed.
Projects
None yet
Development

No branches or pull requests

4 participants