NullReferenceException thrown in Startup.cs, ASP.NET Core about templates HOT 4 CLOSED

This seems to be behaviour that has changed from RC2 to RTM. You can have a look at the linked changeset for details of the change (Other refactoring is included).

Strangely in my testing I was getting the opposite behaviour which is why I did not catch it. After using a different machine I get the behaviour you are seeing.

I've released the fix to the project template. However, I've just realized that NWebSec is still using the old RC2 version. I've really made a hash of this release this time. You can look at NWebsec/NWebsec#59 to see when that package gets updated and then just upgrade it.

from templates.

I pushed new packages just now, upgrade away. :)

from templates.

Thanks for fixing it :) ! I'd have given a PR but I wasn't sure how you'd approach fixing it... and was myself new to both RC2 and RTM (all my projects are waiting to be migrated from RC1, once I get a proper handle on things). Glad I managed to bring it to your attention at least: odd how one machine did and and other didn't - any clue as to why? Method invocation ordering reaaaaaallly shouldn't differ between computers - right?!

@klings As an aside, thank you for making NWebsec, it's a great library.

from templates.

I didn't expend any time looking into it. I added a IOptions constructor RedirectToCanonicalUrlAttribute. In the past this was not possible as you could not have multiple constructors in ASP.NET IOC. Not sure when that changed.

Thanks @klings NWebSec also updated!!!

from templates.