Explore >> Select a destination
|
You are here 
|
adamstorr.co.uk | ||
| | | | |
nodogmablog.bryanhogan.net
|
|
| | | | | In part two of this series you will see how to perform constructor and method dependency injection on simple AWS Lambda functions (deployed with `dotnet lambda deploy-function`) using the new Amazon.Lambda.Annotations library. | |
| | | | |
csharp.christiannagel.com
|
|
| | | | | ASP.NET Core included the WebHost class that was used in the Main method to startup everything up - including the dependency injection container. With Non-ASP.NET Core applications I used the same DI container (Microsoft.Extensions.DependencyInjection), but I had to create the ServiceCollection on my own. This changes with .NET Core 3.0 and the new Host class... | |
| | | | |
vannevel.net
|
|
| | | | | With the release of Visual Studio 2015 RC, we also received the pretty much final implementation of the Diagnostics implementation. This SDK allows us to create our own diagnostics to help us write proper code that's being verified against those rules in real-time: you don't have to perform the verification at a separate build-step. What's more is that we can combine that with a code fix: a shortcut integrated in Visual Studio that provides us a solution to what we determine to be a problem. | |
| | | | |
weblog.west-wind.com
|
|
| | | ASP.NET Core Authentication and Authorization continues to be the most filddly part of the ASP.NET Core eco system and today I ran into a problem to properly configure JWT Tokens with Roles. As I had a hard time finding the information I needed in one place and instead ended up with some outdated information, I'm writing up a post to hopefully put all the basic bits into this single post. | ||
