Third article from my Build 2018 series focuses on day 2 of the conference. We will go through all the cool things from the first keynote, check out a few talks, get the best burger in Seattle and finish ourselves off with some yummy ice cream. Stay tuned!
The x:Name attribute in XAML creates named fields that you can use to access the controls from the code-behind. However, as opposed to WPF, in UWP these fields are private which means you can access them from the code-behind only, not from other classes. While noting it is a good idea from architectural standpoint, is
While working on an UWP app, I wanted to create a string.Format based value converter, so that I could provide a format string in the ConverterParameter , augment the data bound value with it and use the result as a key for a localized string from resources. When I tried to build the project however, I was met
Updated November 2016 – .NET Framework 4.6.2 Windows Presentation Foundation (WPF) apps have a bit harder life in the touch-enabled world. In WinRT apps, the touch keyboard shows up automatically when a text field gets focus so that the user can type without the need of a classic keyboard (no interrupting of her touch workflow). For