My companion post to Zac's post on using a client side React.js application to communicate with a .NET Core powered WebApi. This article was originally posted on The Reactionary.
Microsoft's cloud hosting service, Azure, is really powerful. Visual Studio 2017 hooks directly into Azure, as does the .NET Core tooling. With that in mind, we're going to publish a WebApi application to Azure and watch it fly.
A little different this week. Zac (http://thereactionary.net), Paul (http://codeshare.co.uk), James (http://cynicaldeveloper.com) and myself took part in #Hack24 this year, our team was called AbstractSausageFactory(). Want to find out how we did? You'll have to click through and read this post, won't you?
The final part in our multi-post tutorial on using WebApi with Entity Framework Core. This week we're doing a little refactoring to add our Join table, Shadow Properties and the ability to Seed the database from a series of json files.
The penultimate part in our multi-post tutorial on using WebApi with Entity Framework Core. This week we'll be adding our Character class and service, a Character controller, a little refactoring, and creating POCOs for our Book and Character models
The second part in our multi-post tutorial on using WebApi with Entity Framework Core. This week we'll be adding an initial database migration, adding some seed data, building a Book service, and returning book JSON data in our Book controller