| |
browse.develop.com
Browse.develop.com is a community that was established to collect and
organize valuable web information. Our technical staff have selected and
indexed information and courses that they feel will help you stay
current on best practices across the SDLC.
|
10 Articles match "Runtime","WPF"
| Related DevelopMentor Courses | MORE | | Guerrilla.NET (US) Training WPF/SL : Develop cutting-edge UIs with Windows Presentation Foundation and Silverlight including coverage of Silverlight 5.0 MVVM : Learn advanced WPF / Silverlight design patterns and techniques including MVVM (Model-View-ViewModel). iOS : Build multi-touch enabled applications on platforms such as WPF, Silverlight, and Apple's iPhone / iPad. WPF/SL : Develop cutting-edge UIs with Windows Presentation Foundation and Silverlight including coverage of Silverlight 5.0 Main Topic Day 1 Introduction to WPF and Silverlight (version 4.0 dynamic typing from C# 4.0, DevelopMentor Courses - Tuesday, March 1, 2011 Mark Smith: Dynamic type binding in WPF 4.5 One of the new features in WPF 4.5 This enables adding dynamic properties to types where the actual shape of the type is not known until runtime. is data-binding support for ICustomTypeProvider. For example, where the data itself is being … Continue reading → DevelopMentor Courses - Saturday, March 10, 2012 NET 3.5 & 4.0: LINQ/EF, WCF, WPF/SL, MVVM, MEF Training Design WPF and Silverlight applications using the MVVM design pattern to separate application logic from presentation and facilitate Test Driven Development (TDD). Windows Presentation Foundation (WPF) and Silverlight (SL), Windows Communication Foundation (WCF), Entity Framework (EF) and WCF Data Services (OData). On the client side, you will get an introduction to WPF and Silverlight 4, which have new features aimed at developing business apps, and to WCF RIA Services, which allows you to rapidly build rich Internet apps that include end-to-end data validation. & 4.0 DevelopMentor Courses - Wednesday, February 22, 2012 |
22 Articles match "Runtime","WPF"
| The Latest from DevelopMentor | MORE | | Join Me at Guerrilla.NET in November Learn to write code using new.NET class libraries like Entity Framework 5, MVC 4, and even the new Windows Runtime (WinRT). Model-View-ViewModel for WPF and Metro. Just a quick announcement for an developer upcoming event I’ll be participating in… Early November I’ll be co-teaching DevelopMentor’s biggest.NET developer event of the year in Los Angeles: Guerrilla.NET. If you haven’t been to Guerrilla.NET, it’s a very unique and memorable event – it’s unlike almost any other training class you’ve seen. hope to see you there! Michael C. Kennedy's Weblog - Tuesday, September 25, 2012 Type-Safe Two-Way Data Binding with INotifyPropertyChanged Anyone who’s developed a UI application using Windows Forms, WPF or Silverlight is probably aware that you have to implement the INotifyPropertyChanged interface to get two-way data binding between UI elements and an underlying data source. If you were to change the property name and forget to update the string, the bindings would break without even the benefit of a runtime exception. The problem is that you have to pass the name of the property as a string when you fire the event from each property setter. You can download the code for this blog post here. null ). Body).Member.Name; Tony and Zuzana's World - Tuesday, January 25, 2011 Type-Safe Two-Way Data Binding with INotifyPropertyChanged Anyone who’s developed a UI application using Windows Forms, WPF or Silverlight is probably aware that you have to implement the INotifyPropertyChanged interface to get two-way data binding between UI elements and an underlying data source. If you were to change the property name and forget to update the string, the bindings would break without even the benefit of a runtime exception. The problem is that you have to pass the name of the property as a string when you fire the event from each property setter. You can download the code for this blog post here. csharpcode.alt. {. Tony and Zuzana's World - Tuesday, January 25, 2011 | -
| The Best from DevelopMentor | MORE | - WPF MVVM Helper Library (WPF + MVVM = testability)
There's been a lot of talk about the Model-View-ViewModel pattern recently and it's usage around the WPF and Silverlight technology stack. When teaching WPF, I always introduce students to MVVM as part of the Essential WPF class, it's an incredibly useful pattern that really separates the UI from the code behind behavior. It's evolution owes a lot to various blog posts, WPF Disciples, and other WPF leaders; I certainly didn't invent anything radically new but borrowed heavily from all kinds of places as I built various classes I needed for my own work. file -. - Part 3: Shifting focus to the first available element in WPF
We've seen how to programatically control focus and that's all great stuff, but one thing I like to do with WPF is see how much of the repetitive or UI-specific code I can move into the XAML and keep out of the code behind. They allow for dynamic property assignment - where the value is determined at runtime vs. XAML compile time. That's exactly what I need here - I want to find that TextBox at runtime and shift focus to it - just like I would have done in the code behind. Tags: NET;WPF So it might seem we are stuck with adding code behind logic (blech!) - Part 2: Changing WPF focus in code
In the last post , I wrote about how focus is generally managed in WPF - we have focus scopes to track a single element within that scope for logical focus, and then one of those elements is given physical, or keyboard focus. Keyboard focus is most often set through runtime activity - the user clicks on an element, or uses the TAB key to move around the UI. First, there is a Keyboard class in WPF which exposes several methods and properties. However, the most common request is to set initial focus to a specific control - remember that WPF doesn't do that by default. Mark's Blog of Random Thoughts - Thursday, September 4, 2008 - Part 2: Changing WPF focus in code
In the last post , I wrote about how focus is generally managed in WPF - we have focus scopes to track a single element within that scope for logical focus, and then one of those elements is given physical, or keyboard focus. Keyboard focus is most often set through runtime activity - the user clicks on an element, or uses the TAB key to move around the UI. First, there is a Keyboard class in WPF which exposes several methods and properties. However, the most common request is to set initial focus to a specific control - remember that WPF doesn't do that by default. Mark's Blog of Random Thoughts - Thursday, September 4, 2008 - Using Model – View – ViewModel with Silverlight
have found it extremely easy to use when developing very different applications and have used the design pattern recently in both ASP.NET, WPF and Silverlight applications. Josh Smith did an excellent screen cast for Pixel8 on using MVVM with WPF, you can find it here. All UI control properties that need to change at runtime do so by data binding to a ViewModel property. Tags: NET DevCenter WPF Silverlight The View – Model – ViewModel design pattern, also known as MVVM, is getting more popular these days. The View is data bound to a ViewModel. 11: {. 13: set. 14: {. The Problem Solver - Tuesday, April 7, 2009 - Part 3: Shifting focus to the first available element in WPF
We've seen how to programatically control focus and that's all great stuff, but one thing I like to do with WPF is see how much of the repetitive or UI-specific code I can move into the XAML and keep out of the code behind. They allow for dynamic property assignment - where the value is determined at runtime vs. XAML compile time. That's exactly what I need here - I want to find that TextBox at runtime and shift focus to it - just like I would have done in the code behind. Tags: NET WPF So it might seem we are stuck with adding code behind logic (blech!) - MVVM: Views and ViewModels
Views are the UI presentation of data - in the case of a WPF/Silverlight application this is most commonly the XAML and XAML code behind files (they are considered a single element together). That way, my ViewModel sticks with base (non-WPF) types. This is necessary under WPF 3.5 This is useful when you are dynamically linking things together at runtime vs. compile time. Tags: NET Code MVVM WPF In the previous post, I provided a link to the project template you can use to start a new MVVM project using the JulMar MVVM library. Project Template. Dependencies. %>
| |   |
