As you may know you cannot use ILMerge to merge assemblies with XAML (WPF application) however there is a little known trick you can use to achieve your goal in a bit different way.

This part of the application has four “screens” or PivotItems of data. If we take a look at the application bar (in green at the bottom), then we will quickly notice the following: Contact Details – Contains a cancel and next button. Interest – Contains a previous, cancel and next button. Subscriptions – Contains the same thing as interest. Request Follow Up – Contains previous, cancel, save and close and save and add new. We will quickly see that our standard application bar will not work and that we will need to dynamically load a new application bar as the user swipes to the next page.

Many curious customers send us tickets every week to ask us how they can implement a menu similar to that on our official website, www.telerik.com, using RadMenu for ASP.NET AJAX. The following post is inspired by them and is aimed at providing you with tips and code snippets to help you achieve this appearance and functionality.

Every developer has found him or herself in the situation where a control is missing the one feature that would be perfect in a specific situation or they would love to have a slightly different behavior of an existing feature. This is where attached properties come in handy. Attached properties could be used to extend the functionality of a control with very little implementation on our side. In this blog post I will demonstrate how to implement some basic attached properties in specific scenarios to extend the functionality of a WPF / Silverlight control.

A key advantage Fiddler has over a traditional packet sniffer or in-browser network monitor is the ability to modify the traffic. This can be done manually (using breakpoints and Inspectors) or automatically, using FiddlerScript or extensions. In today’s post, I’d like to introduce one such extension—ContentBlock