.NET Core Running on IIS
I'm configuring an application that we've migrated to .NET Core. It's hosted on Windows Virtual Machines running IIS. It seems like an easy task, right? It has many challenges. The published folder of my application has a wwwroot directory which my IIS application would point to in the past. Not anymore. The web.config in the root folder points to the application's executable. One thing to note is that it also requires a new module AspNetCoreModule and if you don't have it installed you'll get a 404 response. <?xml version="1.0" encoding="utf-8"?> <configuration> < »
I always liked using the latest and greatest and in most of the cases this choice comes as a great challenge. We started building a project a couple of years ago in ASP.NET vNext (or whatever they called it at the time) beta4 with all the latest tooling: dnvm, dnx, dnu, etc... We were not brave enough at the time to use Entity Framework 7 for obvious reasons, it was simply not ready, so we used EF6 and it was kind of happy days until we were ready to release the first version of the application and ready to 
This idea came on one of the Angular Hack Days where I wanted to create something to present by the end of the day where I could get everyone involved. The game is quite simple, everyone will load the page and as people connect to the site more glasses of beer will show up on the screen, as you tap or click the amount of beer in your glass will decrease, the first person to empty their glass wins the game. That's what you see when you have the app running with 3 people connected to it: Of course, I