Creating a demo Web API, with a couple of resources that support the common HTTP methods and use custom JSON representations is now a rather easy task on the majority of frameworks.
However, the real challenges of developing and evolving a production grade Web API are beyond those first steps. How do we design, produce and evolve the output representations? How do we document the Web API, namely what are the roles of description formats such as Swagger? How do we organize code into controllers, actions and other components? How do we evolve the API without breaking the clients in order to cope with changing business needs? How do I control the accesses to the API, namely based on the identity of the requesters? How do I represent error responses?
These are some of the questions that Web API developers and architects commonly face and that we address in this session, based on what the Web architecture has to give us and on the new ASP.NET 5 framework.
In this interactive session, we create an application in C# and XAML. Upon building the app there are multiple areas we explore, however the choice of where this session leads is up to the audience. The application will be broken down into multiple scenarios and as the product owners you get to decide what we implement. Topics the users can choose from include using Sensors, Toast Notifications, User Information with Roaming Profiles, Live Tiles and Globalization, to name a few. This talk may require audience participation through the use of mobile devices.