This is part 2 of a series of screencasts illustrating some of the ideas found in “Prism” or the “Composite Application Guidance” from the Patterns and Practices team that can be used to build Silverlight applications in a way that lends itself to testability and modularity. In talking to customers building business applications with Silverlight I find that Prism (and it’s friend Unity) is frequently mentioned but not everyone has seen it and so I thought I would explore it myself and capture some of the results of that exploration here. We start off with some fairly basic code which we move towards making use of dependency injection and modularity.
