DCSIMG
Order in Chaos,DEV - Arik Poznanski's Blog

Arik Poznanski's Blog

It CAN be done with .NET

News

MVP

MCC

CodeProject MVP

MCPD

MCTS

Subscribe to my blog by email

Arik Poznanski LinkedIn Profile

Email: arik.com at gmail dot com
or, use this form

Locations of visitors to this page


Sela Group

Sela Canada

DZone MVB

Links

Official Blogs

WPF / SL Blogs

Developers Blogs

Browse by Tags

All Tags » Order in Chaos » DEV (RSS)
Order in Chaos: Handling unhandled exceptions in a WPF application
Introduction So you want to handle somehow all the unhandled exceptions in your application. Usually you want to accomplish one of the following: Log the exception for later diagnostics Present the user an unhandled exception UI, nicer than the default You heard there’s an event you should register, or maybe you find one by mistake, but is it the correct one? Did you know there are four (!) different events for handling unhandled exceptions in the .NET framework? So what is the difference between...
Order in Chaos: Dependency Property Value Resolution
One of the strength points for WPF is the ability to set a property value using a wide range of methods. Unfortunately, this variety makes it hard to understand how a WPF dependency property gets its final value. Hopefully this post will help organize this issue. This post is based on the comprehensive MSDN article “ Dependency Property Value Precedence ”. Long Story Short Can you show an example please? In order to see this in action let’s create a WPF application that has all these scenarios used...
Order in Chaos: .NET Collections
This is a review of the current available collection types in .NET Framework 4.0 Note that I don’t plan to explain all the history of the different collection. If a class is obsolete, that is enough information. The intention is to use this post as a reference when you need to decide which type of collection you should use. Also, I’m not going to give the complexity of each function. You can find such information in the relevant class documentation on MSDN. Anyway, you can deduce it yourself, since...