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

WPF Bug or not? #2543

Open
tvv91 opened this issue Feb 8, 2020 · 5 comments · May be fixed by #8853
Open

WPF Bug or not? #2543

tvv91 opened this issue Feb 8, 2020 · 5 comments · May be fixed by #8853
Labels
Bug Product bug (most likely) 🚧 work in progress
Milestone

Comments

@tvv91
Copy link

tvv91 commented Feb 8, 2020

Issue Title

System.Windows.Markup.XamlParseException after removing Style definition in App.xaml

General

I'm found an article for building MVVM WPF app here: https://marcominerva.wordpress.com/2020/01/07/using-the-mvvm-pattern-in-wpf-applications-running-on-net-core

Need to download project https://1drv.ms/u/s!Aj5GOysOGfFKl8JVGGa79K0VMW2Fcg?e=dyhVBW

In the App.xaml on lines 17...19 <Style> definition. If remove them, then get an exception

System.Windows.StaticResourceExtension.ProvideValueInternal(System.IServiceProvider, bool)
System.Windows.StaticResourceExtension.ProvideValue(System.IServiceProvider)
MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(System.Windows.Markup.MarkupExtension, System.IServiceProvider)

And inner exception that static resource 'Locator' not found.

@carlossanlop
Copy link
Member

@gomathip02 @vatsan-madhavan Can you please help here?

@vatsan-madhavan vatsan-madhavan transferred this issue from dotnet/core Feb 10, 2020
@gomathip02 gomathip02 added the Question General question, not a problem in source code or documentation (yet) label Feb 11, 2020
@rladuca rladuca removed the Question General question, not a problem in source code or documentation (yet) label Feb 11, 2020
@rladuca
Copy link
Member

rladuca commented Feb 11, 2020

Clearing this for triage and investigation. This is definitely a regression from .NET Framework behavior on the same code base.

FYI: @SamBent @vatsan-madhavan

@gomathip02 gomathip02 added Bug Product bug (most likely) regression status: This issue is a regression from a previous build or release labels Feb 13, 2020
@rladuca
Copy link
Member

rladuca commented Feb 18, 2020

Actually I re-created this project in .NET Framework and I saw the same behavior. I don't believe this is a regression. (See https://github.com/rladuca/WpfNetCoreMvvm)

@rladuca rladuca removed the regression status: This issue is a regression from a previous build or release label Feb 18, 2020
@rladuca rladuca removed their assignment Feb 18, 2020
@tvv91
Copy link
Author

tvv91 commented Feb 18, 2020

Actually I re-created this project in .NET Framework and I saw the same behavior. I don't believe this is a regression. (See https://github.com/rladuca/WpfNetCoreMvvm)

Actualy, it's my first report on github, I don't know what to do next...

@ThomasGoulet73
Copy link
Contributor

This bug should be fixed by #8853. For now, you can workaround this issue by adding a dummy item in <Application.Resources>.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Product bug (most likely) 🚧 work in progress
Projects
None yet
6 participants