You've seen the demos, read the articles and perhaps even started to use SignalR in a project, but now you're ready for the nitty gritty. What are the best patterns for using SignalR in a real application? How do you deal with users and authorization? How does it work with your favorite IoC container? How do you flow data from back-end systems to SignalR clients? How do you successfully self-host SignalR along side other OWIN compliant frameworks like Nancy and ASP.NET Web API? Damian and David from the SignalR team will answer these questions and more on stage by doing what you do: writing code.
A new major version of SignalR is already here and some things have changed (for the better!). Along with the requisite performance and stability improvements there's even tighter integration with OWIN, .NET 4.5 server dependency, full support for self-hosting, new clients, massively improved cross-domain/CORS support, API usability improvements, easier hub unit testing and better error handling. We'll cover all this and give a sneak peak and new features in upcoming releases in this information packed session.
Does the architecture of your application tell you the intent of the application, or does it just tell you what frameworks you’ve used. A good architecture screams about the intent of the application and hides the frameworks. In this talk, Uncle Bob talks about the lost years of architecture, about how the web is just a detail, and about the best kind of architecture to use for your applications.
Let's do a deep dive into the first of the SOLID principles. What is a responsibility? Why should it be single? How do we make it single? We'll examine all these issues in extreme detail. We'll look at some old code to see whether it conforms or not. We'll also look at various design patterns and strategies that help us conform to this principle.