asp.net-core-3.1

问题 Using ASP.NET Core 3.1 I am creating an User's Email confirmation token to send by email: String token = await _userManager.GenerateEmailConfirmationTokenAsync(user); And I get the following: CfDJ8IjJLi0iO61KsS5NTyS4wJkSvCyzEDUBaVlXCkbxz6zwI1LocG8+WPubx5Rvoi4tFuiWAVFut4gfTnhgsdihE0gY+o7JyJrNtfXmzGLnczwbKZ3Wwy15+IUEi1h2qId72IRKvFqBSFv7rJdECSR/thZphpTQm7EnOuAA7loHlQFRWuMUVBce8HUsv1odbLNsKQ== How can I create shorter tokens with a small lifespan instead of huge tokens? 回答1: If I understand the

问题 We are about to use the built-in in-memory cache solution of ASP.NET Core to cache aside external system responses. (We may shift from in-memory to IDistributedCache later.) We want to use the Mircosoft.Extensions.Caching.Memory's IMemoryCache as the MSDN suggests. We need to limit the size of the cache because by default it is unbounded. So, I have created the following POC application to play with it a bit before integrating it into our project. My custom MemoryCache in order to specify

问题 We are about to use the built-in in-memory cache solution of ASP.NET Core to cache aside external system responses. (We may shift from in-memory to IDistributedCache later.) We want to use the Mircosoft.Extensions.Caching.Memory's IMemoryCache as the MSDN suggests. We need to limit the size of the cache because by default it is unbounded. So, I have created the following POC application to play with it a bit before integrating it into our project. My custom MemoryCache in order to specify

问题 I have just upgraded from .NET Core 2.2 to 3.1. I have tests to confirm that extension methods I've added to HttpContext.Request are working. I was previously able to do things like: var context = new DefaultHttpContext(); var c = new Dictionary<string, string> {{"test", "passed"}}; context.Request.Cookies = new RequestCookieCollection(cookies); var result = context.Request.GetPrimedValue(); Is this impossible now? I tried using Moq for this, but there are far too many things blocking me from

问题 I have just upgraded from .NET Core 2.2 to 3.1. I have tests to confirm that extension methods I've added to HttpContext.Request are working. I was previously able to do things like: var context = new DefaultHttpContext(); var c = new Dictionary<string, string> {{"test", "passed"}}; context.Request.Cookies = new RequestCookieCollection(cookies); var result = context.Request.GetPrimedValue(); Is this impossible now? I tried using Moq for this, but there are far too many things blocking me from

问题 I have below config with empty connection string, "ConnString": { "Value": "" }, Now in Asp.Net Core 3.1 app I am trying to set the connection string value inside CreateHostBuilder public static IHostBuilder CreateHostBuilder(string[] args) => Host.CreateDefaultBuilder(args) .ConfigureWebHostDefaults(webBuilder => { webBuilder.ConfigureAppConfiguration((context, config) => { var settings = config.Build(); settings["ConnString:Value"] = "MY CONNECTION STRING"; }); webBuilder.UseStartup<Startup

问题 I'm trying to add optional claims using Microsoft Identity Web - NuGet for user authentication in NET Core 3.1 WebApp. Reading the MS Docs, it seems that the only steps needed are to declare the optional claims within the App Registration Manifest file in Azure. But when testing the login process using two different apps (my own code and an MS project example) it looks like the optional claims are not being added to the ID Token when returned from Azure following a successful login i.e they

问题 I'm trying to add optional claims using Microsoft Identity Web - NuGet for user authentication in NET Core 3.1 WebApp. Reading the MS Docs, it seems that the only steps needed are to declare the optional claims within the App Registration Manifest file in Azure. But when testing the login process using two different apps (my own code and an MS project example) it looks like the optional claims are not being added to the ID Token when returned from Azure following a successful login i.e they

问题 I'm trying to add optional claims using Microsoft Identity Web - NuGet for user authentication in NET Core 3.1 WebApp. Reading the MS Docs, it seems that the only steps needed are to declare the optional claims within the App Registration Manifest file in Azure. But when testing the login process using two different apps (my own code and an MS project example) it looks like the optional claims are not being added to the ID Token when returned from Azure following a successful login i.e they

问题 I'm trying to gracefully terminate a ASP.Net Core 3.1 service (which will run in Kubernetes). When Kubernetes stops a service, it will send a SIGTERM event to the application, at which point I want in-flight requests to complete (which may take several seconds) before terminating... I think I can catch this in a hostedservice, as below, and hence not stop immediately. The following works, but with a timeout of 5 seconds or longer, I receive an OperationCanceledException. Could anyone shed any