A quick tip to save you a little frustration.

As new ASP.NET Core releases drop at regular intervals, you may find when you upgrade your app that everything works beautifully on your machine but then blows up spectacularly when you upload it to Azure.

You’ll start seeing 500 errors about bad gateways and your app fails to start.

This is often because the version of ASP.NET core you’re targeting hasn’t been deployed to Azure yet.

Good news, you can easily check this for yourself.

Head on over to your app service in the Azure portal, find the Console option in the left-hand menu.

Type dotnet --info and behold, a handy list of precisely which versions of ASP.NET Core are available to your app.

Stuck every time you jump out of the tutorials?

Make 2019 the year you finally conquer all those controllers, views, models and all that other "stuff" that comes with MVC.

You'll also get ASP.NET advice, guidance and useful tips from me once a week (or so). I respect your email privacy, unsubscribe at any time.

Stuck every time you jump out of the tutorials?

Stop wasting time trying to learn ASP.NET Core MVC and fast forward to the fun bit (building your features)

Can't make sense of front-end development?

Check out Front-end in four hours for a head-start

Take a look

Stuck every time you jump out of the tutorials?

Make 2019 the year you finally conquer all those controllers, views, models and all that other "stuff" that comes with MVC.

You'll also get ASP.NET advice, guidance and useful tips from me once a week (or so). I respect your email privacy, unsubscribe at any time.