Skip to main content

WPF is still alive!

With all the fuzz about the dead of Silverlight, we should almost forget that it still has a big brother WPF.

After the announcements at Build it looks like that WPF isn’t dead either. It even has some very useful new and enhanced features

  • Ribbon control: WPF 4.5 ships with a Ribbon control that hosts a Quick Access Toolbar, Application Menu, and tabs.
  • Improved performance when displaying large sets of grouped data
  • New features for the VirtualizingPanel
  • Binding to static properties: You can use static properties as the source of a data binding. The data binding engine recognizes when the property's value changes if a static event is raised.
  • Accessing collections on non-UI Threads: WPF enables you to access and modify data collections on threads other than the one that created the collection. This enables you to use a background thread to receive data from an external source, such as a database, and display the data on the UI thread. By using another thread to modify the collection, your user interface remains responsive to user interaction.
  • Synchronously and Asynchronously validating data: The INotifyDataErrorInfo interface enables data entity classes to implement custom validation rules and expose validation results asynchronously. This interface also supports custom error objects, multiple errors per property, cross-property errors, and entity-level errors.
  • Automatically updating the source of a data binding: If you use a data binding to update a data source, you can use the Delay property to specify an amount of time to pass after the property changes on the target before the source updates.
  • Binding to types that Implement ICustomTypeProvider
  • Retrieving data binding information from a binding expression
  • Checking for a valid DataContext object
  • Repositioning data as the data's values change (Live shaping): A collection of data can be grouped, sorted, or filtered. WPF 4.5 enables the data to be rearranged when the data is modified.
  • Integrating WPF with win32 Graphical User Interfaces(My favorite!): WPF 4.5 provides better integration between WPF and Win32 user interface components.
  • Improved Support for Establishing a Weak Reference to an Event: Implementing the weak event pattern is now easier because subscribers to events can participate in it without implementing an extra interface. The generic WeakEventManager class also enables subscribers to participate in the weak event pattern if a dedicated WeakEventManager does not exist for a certain event.
  • New methods for the Dispatcher class: The Dispatcher class defines new methods for synchronous and asynchronous operations.
  • Markup Extensions for Events: WPF 4.5 supports markup extensions for events. While WPF does not define a markup extension to be used for events, third parties are able to create a markup extension that can be used with events.

More information and all the details here: http://msdn.microsoft.com/en-us/library/bb613588(v=VS.110).aspx.

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.