In this post, I'll discuss the process I took to go from the dotnet new command all the way to a single page application which sends GET requests, parses the responses and uses Angular2 to display rich, human readable versions of the parsed data
The dotnet new command has support for project templates, and one of the template packages that Microsoft has released contains a collection of Single Page Applications. In this post, I’ll take us through how to make a new project from the Angular2 template, what changes where made the .NET Core to make some of the more impressive things in this template work, and how it all fits together.In this post, I talk you through how to create an Angular2 Single Page Application from one of these templates and how it all fits together.
Microsoft provide a few IDEs (VS Code being cross platform too - which is a first), but which should you use for .NET Core development and how do you choose? What are the official tooling options available when you are forced to choose between them?
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.
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