XamlCSS.WPF 2.2.0

.NET Framework 4.5.1 This package targets .NET Framework 4.5.1. The package is compatible with this framework or higher.
There is a newer prerelease version of this package available.
See the version list below for details. 
dotnet add package XamlCSS.WPF --version 2.2.0                

                    
                

            
NuGet\Install-Package XamlCSS.WPF -Version 2.2.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="XamlCSS.WPF" Version="2.2.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add XamlCSS.WPF --version 2.2.0                

                    
                

            
#r "nuget: XamlCSS.WPF, 2.2.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install XamlCSS.WPF as a Cake Addin
#addin nuget:?package=XamlCSS.WPF&version=2.2.0

// Install XamlCSS.WPF as a Cake Tool
#tool nuget:?package=XamlCSS.WPF&version=2.2.0

XamlCSS

Style Xaml-applications with CSS - get it for WPF, Xamarin.Forms or UWP and start right here!

Why XamlCSS For XAML?

Concise

Styling with (s)css gives a more concise declaration of your styles. XamlCSS even supports a subset of SCSS features like selector nesting, css-variables and mixins. This enables you to make your declarations even more concise.

Freely Combine Styles

Other than vanilla Xaml-styles, css allows you to freely combine styles - no BasedOn restriction. Even better, this is done for you behind the curtains!
And if you really want to combine styles yourself use @extend.

Semantic Meaning

Semantic meaning can be conveyed, i.e. is your ui-element important, a warning, a header or a sub-header? This is achieved by using css-classes.

Based On View-Hierarchy

Css takes into account where inside your view-hierarchy your element gets added. No need to manually assigning a style.
It also detects that an element was added or removed.
In combination with semantic selectors you can style a button differently just because it is in a warning dialog. And if you want to create a dark, a light and a custom theme, just switch the css-class-name on your root view-element and all elements update themselves automatically.

Support For Xaml-Features

You can use markup-extensions and triggers in your (s)css.

In css you cannot declare an instance of an object as you can do in xaml. A Storyboard for example must be declared as usual in a ResourceDictionary but then can be referenced in css with a markup-extension.

Designer Support

XamlCSS builds on top of the native Xaml-Style implementations, so it works with the WPF and UWP designer. For Xamarin.Forms there is LiveXAML.

Supported platforms

Supported Features

  • CSS selectors
  • Remove and reapply styles
  • Detect new elements and apply matching styles
  • Support Binding * (except vanilla UWP)
  • Support StaticResource *
  • Support DynamicResource * (except vanilla UWP)
  • Set simple values like Foreground, FontSize, FontStyle,... by CSS
  • Triggers
  • Multiple StyleSheets
  • Nested selectors (like Sass)
  • Css-variables
  • Import of other css-files
  • Mixins

Not (yet) supported

  • Visual State Manager

For more information look at the provided test-apps in the solution to see how to initialize and use XamlCSS.

*) Breaking change in binding syntax in 2.0.0: instead of {Binding value} you now write #Binding value or "{Binding value}"

Product Compatible and additional computed target framework versions.
.NET Framework net451 is compatible.  net452 was computed.  net46 was computed.  net461 is compatible.  net462 was computed.  net463 was computed.  net47 was computed.  net471 is compatible.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

  • .NETFramework 4.5.1

  • .NETFramework 4.6.1

  • .NETFramework 4.7.1

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.2.1-pre2 497 5/1/2020
2.2.1-pre1 468 4/4/2020
2.2.0 1,750 2/10/2019
2.2.0-pre7 744 9/5/2018
2.2.0-pre6 682 8/31/2018
2.2.0-pre5 851 5/12/2018
2.2.0-pre4 779 5/6/2018
2.2.0-pre3 925 5/1/2018
2.2.0-pre2 772 4/30/2018
2.2.0-pre1 839 2/11/2018
2.1.0 1,324 12/9/2017
2.0.1 1,076 7/23/2017
2.0.0 1,056 5/21/2017
2.0.0-pre1 857 2/9/2017
1.0.6 1,051 1/22/2017
1.0.5 992 1/21/2017
1.0.4 1,063 12/18/2016
1.0.3 1,033 11/29/2016
1.0.2 1,047 11/29/2016
1.0.1 991 11/22/2016
0.9.0-beta-1 775 9/10/2016
0.9.0-alpha-5 843 6/27/2016
0.9.0-alpha-4 826 6/26/2016
0.9.0-alpha-3 824 6/24/2016
0.9.0-alpha-2 848 6/17/2016
0.9.0-alpha 878 5/22/2016
0.8.0 1,077 5/21/2016
0.8.0-beta-3 842 5/18/2016
0.8.0-beta 1,300 5/16/2016

2.2.0
           - #32: .NET Standard
           - #82: VisualTree/LogicalTree Match-Optimization Marks Not-Traversed Nodes as Traversed
           - #84: WPF, UWP: :visual-tree Pseudo Selector Not Matching Correctly On Parent Elements

           2.2.0-pre7
           - #80 WPF: Style not applied to Items defined in Template - handle treeviews correctly
           - Live edit: '#' should not crash application
           - Tree-node-matching performance: if general parent selector already matched don't evaluate for elements down the tree

           2.2.0-pre6
           - Attached property "ApplyStyleImmediately"
           - Performance improvement (IsInLogicalTree/IsInVisualTree)
           - Enable global stylesheet with "StyleSheet.IsSharedApplicationStyleSheet"
           - Fixed element-loaded-issues
           - Fixed name not always correctly recognized

           2.2.0-pre5
           - #78 WPF: Children Of Frame Don't See Parent
           - #79 Nth-Selectors With Negative Factor Are Not Handled Correctly

           2.2.0-pre4
           - Major performance enhancements
           - #75 WPF: Setting Class On Window Chrome Element Causes Exception
           - #76 Support Attribute Selectors With Change-Tracking
           - #77 WPF: Support One StyleSheet For Multiple Windows

           2.2.0-pre3
           - #72 StyleSheet Should Update If SingleBaseStyleSheet Changes
           - Removed Measure calls used for exact performance profiling
           - Remove missed debug messages

           2.2.0-pre2
           - #69 Support Selectors With Visual Tree Elements Like ScrollBar: :visualtree selector, logical tree and visual tree
           - #70 WPF: ItemsControl Children Are Not Styled
           - #71 Increase Performance Of Applying Styles: new tree traversing (performance, optimization)
           - #73 Support AOT By Setting Preserve Attribute
           - Wrong universal-selector if not first selector-fragment
           - Pseudo-selector not parsed if combined with another selector (comma separated)

           2.2.0-pre1
           - #52 Attributes Cannot Be Matched - One-Time Matching
           - #53 Asterisk Selector Has Wrong Specificity
           - #54 String Value Throws Exception In Property- And DataTriggers
           - #59 Preview-Friendly Basing StyleSheets On Others
           - #62 Variable Cannot Reference Another Variable
           - #64 Support Xml-Namespace mapping
           - #65 Remove AngleSharp Dependency

           2.1.0
           - #39 Ampersand Could Be Anywhere in Selector
           - #40 Support @extend
           - #42 WPF: Sometimes Skips Styling of Button Content
           - #43 Wrong Selector Generated When Using Ampersand In The Middle Of Selector
           - #44 DataTriggers: Support Custom Markup-Extension-Expressions
           - #45 DataTriggers: Support Variables In Markup-Expressions And Values
           - #46 PropertyTriggers: Support Variables In Value-Expressions
           - #48 Support Parsing Floating Point Numbers Without Leading Zero
           - #49 Support Import Of Css Stored In Application.Resources
           - #50 Css-Parser: Parser Hangs If Document Only Contains "At" Character

           2.0.1
           - #36 Fixed "XamlCSS does not support unicode escapes"

           2.0.0
           - #29 Support comments
           - #30 Support enter/exit trigger actions
           - #31 Better error information
           - Rewritten tokenizer, css-parser (performance, maintainability)
           - Better markup-extension parsing
           - Fixed same selector property overrides
           - Support namespaces in markup-extensions

           2.0.0-pre1
           - #11 Nested selectors, css-variables
           - #23 Css imports
           - #24 Sass-like mixins
           - #27 Support triggers (property, data, event)
           - #28 Fixed bracket parsing

           1.0.6
           - #20 Performance: Selectors are parsed too often

           1.0.5
           - #16 WPF: Resource FontFamily doesn't work in Css
           - #19 Decimal Number not parsed correctly
           - #18 Class not properly parsed in grouped selectors
           - #13 CSS-Parser: Broken String-Literal Handling

           1.0.4
           - Css namespacing support fixed
           - Flickering when control added to view

           1.0.3
           - Fixed NullReferenceException

           1.0.2
           - Xaml-Designer Preview support
           - CssParser Tokenizer fixed
           - Better Logical-/Visual-Tree handling

           1.0.1
           - Define stylesheet in Xaml-files with css text
           - Fixed selector specificity

           1.0.0
           - Performance/memory improvements: Caching dom-elements, dom-children,...
           - Batch-Rendering
           - Define stylesheet in Xaml-files with css text
           - Fixed selector specificity

           0.9.0-beta-1
           - Added better css-quotes support
           - Support modal pages
           - fixed bool value support
           - Fixed VisualTreeCell.Include="true"
           - Performance improvement
           - AngleSharp 0.9.8

           0.9.0-alpha-5
           - Fix partial updates: not finding all parents while executing css-parser

           0.9.0-alpha-3
           - Support more general UI types

           0.9.0-alpha
           - experimental support for MarkupExtensions

           0.8.0
           - Support for attached properties
           - Support for CSS-namespaces