Because SharePoint lists are automatically turned into connectable Web Parts, you can integrate your own Web Parts with any existing SharePoint list by implementing the default interfaces provided by SharePoint.
Peter finishes up his discussion of using the Fakes Framework with TDD in Visual Studio 2012 Ultimate by looking at mocking properties and why you'd want to pass a shim as parameters.
Using shims in Visual Studio 2012 Ultimate lets you easily bypass code—no matter how deeply buried—to test just the parts of your application that you want to test.
One of the major reasons that developers don't like TDD is because, inevitably, it leads to mocking—which can be time consuming. Microsoft has created the Fakes Framework just to simplify the whole process.
The key decisions -- the "architectural" decisions -- in user interface design aren't technical ones. The good news? Just two principles that drive those decisions. The bad news? You won't like either of them.
The difference between Structs and Classes isn't about data vs. code: it's about what happens when you move the data around. And sometimes you want a Struct, not a Class.
Peter returns to the ASP.NET Web API in Visual Studio 2012 to use it with ASP.NET. And this time, he's moving complete objects from the client up to the server in an HTTP POST.
Windows Communication Foundation routing lets you decouple your service consumers and providers to give you the flexibility to modify and extend your services without disrupting your clients.
As you navigate between one View and another using Prism's Navigation API, you'll need to pass data between your Views. Here are the tools you need.
Prism's Navigation API makes it a lot easier to swap Views in and out of regions in your Window -- assuming you give Prism enough information to do the job right.
Windows Presentation Foundation with Prism and Unity makes assembling applications at runtime from loosely coupled Modules easy -- provided you don't have competing Modules and don't need to communicate between them. Here's how to solve those two problems.
There are two strategies that you can follow in pulling together the modules that make up your WPF composable application: Central Control and Distributed Control. Here’s how to implement both of them.
WPF with Prism and Unity allow you to create loosely-coupled applications that assemble themselves at run time. Here's how Prism and Unity allow you to dynamically integrate business logic into your application.
If you're building Windows Presentation Foundation applications that will change over time or have some combination of complex workflows, rich user interaction, and significant presentation or business logic, Microsoft recommends that you add Prism and Unity to your toolkit. That's good advice.