Internal Server Error after Upgrading to .NET Core 1.1

So I decided to start upgrading all my Azure Web Apps and associated NuGet packages to to .NET Core 1.1. The process was very simple and everything worked perfectly locally.

Naturally, I pushed my update to my GitHub repo, Azure takes over and does the deployment. Then.. FAIL

An Error occurred while starting the application.

First thing I try is to re-sync the repo through the admin. No luck. Thankfully though, there is a simple solution.

Turns on when doing the deploy there are left over dll’s in your wwwroot folder that will conflict with your new dll’s. This causes the web app to fail.

To resolve this error, simply do the following.

Stop your web app

Go to your Kudu console either through advanced tools or directly from the scm url.

Go to the CMD or Powershell prompt. Navigate to the /site/wwwroot folder. Delete everything in it!

Go back to deployment options and re-sync your Github Repo

Once this is done start your application and you will be good to go!

Deploy Azure Web App or Azure Function from Repository Folder

I participate in a lot of hackathons. Whether its an internal up-skilling event, university hackathon, or on site with a partner. These are often some of the most fun and frustrating things I get to work on.

At just about every hackathon, we use GitHub to setup a central repo with all the parts of the project we are working on. This could for example contain a web app, azure functions, Xamarin app, console app etc. We normally will just throw everything into its own folder and work from the one repo to keep it easy for everyone.

Often, I want to deploy my web app (and only the web app) right from this repo as I am pushing changes to GitHub. Thankfully through Azure, not only is it very easy to setup continuous deployment using GitHub, but you can also specific what folder within the repo to deploy from.

To deploy an ASP.NET Core web app to Azure from a specific folder in your repository, you simply have to add a new application setting called ‘project’ and point it to the source folder of the project.

For example; I have a project consisting of a UWP slideshow application and my web app to manage the slides. The repository can be found here: https://github.com/joescars/MICMediaSlideshow

In this instance, I only want to deploy the folder ‘MicMediaManager’ to my web app. To do this I connected my Azure Web App to GitHub for continuous deployment and then added the following settings to my app settings.

That’s it! Now I can update each folder independently and my web app will only publish changes within the source folder specified.

So… what about Azure Functions?

This same method works with Azure Functions as well. I’ve setup a sample repository here: https://github.com/joescars/AzureFunctionsCustomDeployment in which I have a folder with my Functions inside their own sub-folder. I then go to the function app settings, add a project setting and it will deploy all my Functions from that folder.

Happy Coding!

Using Google Authentication with ASP.NET Core (ASP.NET 5)

** UPDATE – PLEASE READ **

Please visit: https://docs.microsoft.com/en-us/aspnet/core/security/authentication/social/google-logins for updated instructions on how to use Google Authentication with ASP.NET Core.

The instructions in this article are out of date and I have not yet had a chance to update it.


While speaking with some local developers about ASP.NET Core I was asked if integrating Google Authentication was just as easy in ASP.NET Core, Core MVC (MVC6) as it was in the past. I honestly had not tested it yet so I decided to give it a shot. Thankfully, its very simple, but slightly different, so I’ve included detailed instructions below.

Note; this assumes you have Visual Studio 2015 Update 1 and ASP.NET 5 RC1 Installed. If not you can get both from the following links:

Create a new ASP.NET 5 MVC Project

Go to File -> New Project

1-vs-2015-new-project

Select ASP.net Web Application. Name your App and hit Ok

2-Web-Application-Name

Select Web Application under “ASP.NET 5” Templates

3-select-asp-net-5-web-application

Let Visual studio create the project and automatically restore the packages.

Once the solution loads, hit CTRL+F5 to run your app. Note the URL it runs on and copy this URL as we will use it later.

4-run-project-to-get-url

Setup and Create a new Google OAuth 2.0 Client ID and Secret

Head over to https://console.developers.google.com and sign in with your Google account

05-google-developer-console-home

In the top right click on the “Select a project” drop down and choose “Create a project”

06-google-developer-console-create-project

In the new project dialog that pops up enter a name for your project, agree to the terms and click “create”

07-google-developer-console-name-app

You will now be returned to your dashboard. Click on Enable and Manage API’s

08-enable-manage-apis

In the window that pops up choose the project you just created and hit continue

09-google-select-project

On the next page scroll down and click on Google+ API

10-select-google-plus-api

On the next screens click Enable and then Go to Credentials

11-select-enable

12-goto-credentials

On the Add Credentials screen choose Google+ API and Web server from drop downs. Choose User data under “What data will you be accessing” and click “What credentials do I need”

13-add-credentials

Remember how I had you save the url of your project? There is where we enter it. In the first box enter in the URL and make sure to remove the trailing / . In the second box add the same url but end it with /signin-google . Once you have done this click on Create client ID

14-add-credentials-filled-out

The next screen will let you customize the Google Consent page. This is the page the users see where they have to allow you to access their data. Just enter in a product name for now and click Continue

15-consent-screen

You are now done! Google only shows you the Client ID right away so I will show you how to go back and display your Client ID and Client Secret. First click Done on this screen

16-done-shows-clientid

The next screen shows all the credentials you have setup. Simply click on the first credential name.

17-apps-listed

This screen now shows your Client ID and Client Secret. Make note of both of these because we are going to use them in your project.

18-google-dev-console-shows-clientid-clientsecret

Setup your ASP.NET Core Application with Google Authentication

Now that we have the project setup and your Google Client ID and Secret, we simply need to modify the project to use Google Authentication.

First we need to install the Google Authentication Nuget package. To do this, let’s switch back over to Visual Studio and open up your project.json file. In the dependencies section add the following piece of code to the end.

It should look like this

19-add-google-authentication-package-project-json

Notice that when you do this, Visual Studio will automatically download and install the Nuget package setting up all your reference for you.

20-nuget-auto-restores-package

Now lets open up Startup.cs add add the following code. NOTE: It is important you add this code after app.UseIdentity(); and before app.UseMVC()

It should look like the following. Of course replace the values with your Client ID and Client Secret

21-edit-startup-add-google-auth

Let’s now run the project, CTRL + F5, and click login in the upper right hand corner. You should now see a page similar to the one below.

23-google-auth-consent-screen

Once the user hit’s allow they can authenticate using Google.

Technically we have done everything to get Google Authentication working. But, being I started from a brand new project I am going to continue and show you how to update the database use a migration so that the project will run properly.

Applying a database migration using DNX

If you followed this tutorial from the very beginning and started with a new project, you will get an error after hitting “Allow” similar to the one below.

24-ef-error

How to we fix this? Easy, open up a command prompt in the project folder. Run the command “dnx ef database update”. This will apply the initial database migration.

26-dnx-ef-update

Once you have done that, refresh your page and you are good to go! It should ask you to finish setting up your account and then log you into the site.

27-authentication-success

28-success-google-auth-works-asp-core

I hope you found this tutorial helpful! Happy Coding!

Getting started with ASP.NET Core 1.0

This was presented at South Florida Code Camp 2016.

You can find the code from the demo here: https://github.com/joescars/SFCCASPCoreDemo

In this presentation I walk you through how to get started with ASP.NET Core 1.0. We focus on the cloud and cross platform story.

I walk you through the following:

  • High level overview of ASP.NET Core
  • How to install ASP.NET Core
  • Creating an ASP.NET Core project in Visual Studio
  • Project structure and overview
  • Local debugging and building
  • Pushing the website to Azure using local Git repository

We then switch over to the MAC and continue with the following

  • How to install and configure ASP.NET core and Visual Studio Code on the MAC
  • Pulling the project down to MAC via Git
  • Editing the project in Visual Studio Code
  • Building the project and running locally using Kestrel Web server
  • Pushing the updates back up to Azure using Git