Get the latest nighly NuGet packages with this NuGet feed! https://www.myget.org/F/omnixaml/api/v2 # OmniXAML ## The Cross-platform XAML Framework. [![Join the chat at https://gitter.im/SuperJMN/OmniXAML](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/SuperJMN/OmniXAML?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [![Build status](https://ci.appveyor.com/api/projects/status/yyryrdbik5snckqh?svg=true)](https://ci.appveyor.com/project/SuperJMN/omnixaml) *I know you need it, I know you want it. I know you XAML!* ![Sample](https://cloud.githubusercontent.com/assets/3109851/8272107/1af21840-1837-11e5-85d5-e61c7c8e9679.png "Test Application") **OmniXAML is a library that allows you interpret XAML with ease. You can read XAML and get the object it represents, like a Window in WPF, a document, a diagram or whatever object you can describe.** In its current state it's able to interpret quite complex XAML without problems. It complies with most of the features that XAML provides, except for some uncommon/advanced features like: - x:Class directive - x:TypeArguments - x:Shared It also lacks support for events. OmniXAML doesn't generate compiled XAML, so no intermediate format is produced. Since it's designed to be cross-platform, it doesn't rely on extra build steps. This means that right, in order to have access to named elements (x:Name/Name) you will have to use namescopes, for instance `window.Find(nameOfControl)`. # Using OmniXAML with WPF It's super easy! Just follow this [simple guide](https://github.com/SuperJMN/OmniXAML/wiki/Using-OmniXAML-for-WPF). # Sample XAML The following an example of XAML that can be read with OmniXAML. ```xml