Prism for Windows Runtime: Integrating a Dependency Injection Container

This is the fourth post in a series that walk you through creating a simple Windows Store app using the Prism for Windows Runtime library. Please review the third post in the series for the steps necessary to create the basic MVVM style app based on MvvmAppBase. You can get the latest source on CodePlex….

12

Unit Testing SharePoint 2007 Applications

When developing SharePoint applications, it is common to develop custom: ASP.NET Web Forms WebParts Event Receivers Workflow coding activities One of the first things we noticed when trying to unit test our business logic is that our code will heavily relied on elements of the SharePoint API. SPWeb SPItemEventProperties SPList A common approach to making…

10

Prism 5.0 for WPF just shipped.

Prism version 5.0 for WPF is now available. This version of Prism includes updates to existing and several new NuGet packages: Prism Prism.Composition (New) Prism.Interactivity (New) Prism.Mvvm (New) Prism.MefExtensions Prism.UnityExtensions We’ve updated Prism 4.1 with bug fixes and a few new features. We’ve removed Silverlight support. Windows Phone 8.1 will be supported in a future…

7

Prism for Windows Runtime: Creating and showing a Flyout using the FlyoutService class

This is the third post in a series that walk you through creating a simple Windows Store app using the Prism for Windows Runtime library. Please review the second post in the series for the steps necessary to create the basic MVVM style app based on MvvmAppBase. You can get the latest source on CodePlex….

6

Decoupled Communication with Prism (Commanding)

WPF provides RoutedCommand which is great at connecting command invokers such as menu items and buttons with command handlers that are associated with the current item in the visual tree that has keyboard focus. However we had several scenarios that Prism needed to support where the command handler lived in a controller that had no…

6

Decoupled Communication with Prism (intro)

When building large complex applications, a common approach is to divide up the functionality into discrete module assemblies. Even further it is desirable to not have static references between these modules. This allows the modules to be more easily versioned, tested independently, and promotes decoupled communications. How then can a module work with or leverage…

5

Composite WPF Guidance

A month ago I started working on a new project within patterns & practices: Composite WPF (code name PRISM). If you’re curious about the name PRISM, please read Glenn’s blog entry. We are looking to provide guidance on how to create modular, composible applications on WPF. What are modular, composible applications? Imagine that you want…

5

Decoupled Communication with Prism (Event Aggregation)

In my previous post, I discussed commanding and how you can hook up invokers (e.g. buttons and menu items), global CompositeCommands, and module level command instances. If you need the sending of a message to be initiated by a user gesture such as a button click, Commands may be a good choice. If you need…

5

Prism for Windows Runtime

As Blaine Wastell posted, we are about to release the patterns & practices guidance for building Windows Store business apps. You may be thinking… “What is a business app?” and “How is a business app different than any other app?”. Well the simple answer is that a “business” app is expected to be well architected,…

4

Running VSTS unit tests on WM5 devices

Porting Code and Unit Tests to the device: After much work, we ported the source code and unit tests from the desktop versions of CompositeUI, CompositeUI.Winforms, and ObjectBuilder projects to corresponding Windows Mobile 5.0 Pocket PC projects. We even got the unit tests to pass when run on the VSTS unit tester. We’re done right? Wrong. In…

4