Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
XAML Node Stream: Missing CurrentObject before EndObject
See original GitHub issueDescription
Creating a new Window which has a PNG image in it - I’ve tried as both Icon of the window or as a background image on a child control. The image is a content resource and shows in the WPF designer - but when I run the application, as soon as I create the window, I get: -
An unhandled exception of type 'System.Xaml.XamlObjectWriterException' occurred in System.Xaml.dll Additional information: XAML Node Stream: Missing CurrentObject before EndObject.
Any way I can get around this?
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@isaacabraham workaround - you can just specify assembly:
This is a limitation (ie: necessity) when using FsXaml. Since we’re not compiling the XAML into BAML in the same assembly, at runtime, it’s being loaded outside of the assembly, which requires including the assembly in the
xmlnsdefinitions.I’d like to figure out a way to not require this, but at this point, it’s required to use any resources (whether in the assembly or outside of it).