
WPF
Get flash to fully experience Pearltrees
Creating Inner Shadow Effects for WPF and Silverlight
Introduction If you've ever been tasked with converting a Photoshop design into a WPF UI, you'll probably have tried the Expression Blend Photoshop Import feature. So you'll know that whilst it does a pretty good job of importing simple Photoshop files, it struggles when asked to convert the little flourishes with which designers like to top off their masterpieces. Like Inner shadows. In this article, I'll show you a couple of ways of creating inner shadow effects in WPF, one of which also works for Silverlight. Pleased to meet you, Mr.Showing Dialogs When Using the MVVM Pattern
Contents Introduction This article will address one of the problems a developer might run into when using the MVVM pattern, namely opening dialogs from ViewModels. Basic knowledge of the pattern is expected.XAML Dialog Control: Enabling MVVM and Dialogs in WPF
Introduction Wouldn't it be great if you could use dialogs like any other control in XAML? That is, drop in a <Dialog> element and have a modal dialog window appear? This would let Model-View-ViewModel (MVVM) programs show dialogs without touching the XAML's code behind; a feat not currently possible with Windows Presentation Foundation (WPF). This article presents the Dialog control which both simplifies dialogs and makes them work directly with MVVM.We recently announced that we have discontinued development of Expression Web, Expression Design, and Expression Encoder, and that Blend will be included as a standalone product with Visual Studio. You can read the full announcement on our community page at http://msdn.microsoft.com/expression . The Expression Gallery is now closed and the project files are no longer available. The owners of projects in the Gallery were notified of the closure in advance, and were invited to submit items to the MSDN Gallery or Visual Studio Gallery . Popular Gallery Projects
Expression Zune Borderless Window Behavior
Have you ever used the Zune software? I guess so, but I haven't until version 4.7.1404.0 came out. This version comes with significant changes: Windows Phone 7 support and integration with Windows Live Essentials 2011 among other. When I first run the software I got amazed by the user interface (UI). I told to myself, "this must not be WPF, no way!".
Building a Metro UI with WPF - moodmosaic (Nikos Baxevanis)
Fluent ViewModel Configuration for WPF (MVVM)
Step 1: Define the view model The view model is the contract between the controller and the view. This should have the properties that may be bound to from the view, including any commands (ICommand). Example public interface IDemoViewModel { string Title { get ; set ; } string Text { get ; set ; } long Counter { get ; set ; } IList< string > List { get ; set ; } ICommand Command { get ; set ; } }Julian Dominguez Blog » Blog Archive » ICommand for Silverlight with Attached Behaviors
Silverlight has many things in common with WPF, but also many different or missing things because it is a “subset” of it. One of the missing things is support for the ICommand interface ( UPDATE: in Silverlight 2, this interface was included, but there is no implementation that uses it, so this post is still useful and the sample was updated to use Silverlight’s interface instead of my own copy of it from WPF ). I find this interface (and the button’s behavior when bound to a command) extremely useful/necessary, especially when using DataTemplates bound to a Presentation Model (to provide the view for the model), as hooking events (like Click) is not an option in this scenario. < Button Content ="Save" Command ="{ Binding SaveOrderCommand }" />using System; using System.Windows; using System.Windows.Input;
Functional Fun: Hooking up Commands to Events in WPF
With the introduction of design time data support in Blend I thought that I would try and take advantage of using design time data and MVVM. For a while now I have been using Ninject, with a Service Locator Pattern to provide the ability to build WPF and Silverlight apps in an MVVM pattern where I prefer to use a View first mechanism. There are a number of benefits from using this approach, one of the ones that we are good to drill to in this post is around Blendability of the controls that developers create. Prior to me using Ninject I would have a heavy reliance on the DesignerProperties IsInDesignMode call to check to see if the control was being render in Blend, as i would normally have to do something to stop the control from crashing and allow myself and the designer to use Blend in order for us to Style and Template the controls we created.

