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.
Peter pays a final visit to the WCF 4.5 WebSockets implementation to take advantage of the WebSocketService class and build a service in six lines of code (not counting configuration and client-side code, of course).
Peter Vogel continues his exploration of WCF 4.5's support for WebSockets by writing the code to accept data from the client and then return data to the client whenever that data becomes available.
Peter introduces WCF 4.5's support for WebSockets first by describing why you care and then by setting up to build a bi-directional service using Windows Server 8, and Visual Studio 11.
While Windows Communication Foundation 4.5 has lots of little improvements, the ASP.NET Web API is a very big change. You'll probably end up taking advantage of both, so here's what's in the pipeline for you.