asp.net-core-3.1

问题 I am trying to validate that if a property / field is completely left off on a request that the ModelState is invalid and a BadRequest is sent back to the client, however I am struggling with handling of non-nullable types in request bodies. Works for nullable types [Required] public string NullableString { get; set; } Works for non-nullable and nullable parameters public IActionResult RequiredNonNullableIntQueryString([Required]int nonNullableInt) public IActionResult

问题 I am converting from .NET CORE 2.2 to 3.1. Is it possible to force the controller to use System.Text.Json to serialize and deserialize any incoming request and response? Basically, when the request comes in I want to use System.Text.Json and when a response goes out I want to use System.Text.Json . If yes, how? The reason for doing this is that Microsoft is really pushing this library as the replacement for Newtonsoft.Json as being so much safer and faster. But, I cannot seem to find any

问题 I am converting from .NET CORE 2.2 to 3.1. Is it possible to force the controller to use System.Text.Json to serialize and deserialize any incoming request and response? Basically, when the request comes in I want to use System.Text.Json and when a response goes out I want to use System.Text.Json . If yes, how? The reason for doing this is that Microsoft is really pushing this library as the replacement for Newtonsoft.Json as being so much safer and faster. But, I cannot seem to find any

问题 In Ember Octane, when calling a save on the model, which calls a save to the back-end (.NET CORE 3.1), what is the default accept and content-type headers? I have tried looking online, but I cannot seem to find anything in the documentation. Is it application/json or application/vnd.api+json ? 回答1: It depends on the adapter you are using , the default one is json-api , the latest JSON API specification says Clients MUST send all JSON:API data in request documents with the header Content-Type:

问题 I am trying to create middleware which performs some checking for particular requests. For example, I have such routes: api/Test/{paramToCheck}/aaa api/Test/bbb/ccc and I have these requests: http://some-host-and-port/api/Test/1234/aaa http://some-host-and-port/api/Test/bbb/ccc Now inside my middleware I want to check if request contains {paramToCheck} and get value of this parameter. When I set breakpoint inside InvokeAsync I can see httpContext.Request.RouteValues property containing all

问题 I need to update the .NET Core version for use with Azure Functions. The dotnet command shows that the highest version available is 2.2.402. Checking in the Azure Portal CLI, the .NET Core files are installed in usr/share/dotnet/sdk . I can install .NET Core v3.1.0.2 on my Windows 10 PC, but I can't see how to install into the share/dotnet/sdk folder so that the global.json can reference this version of .NET Core. After installing .NET Core on Windows 10 on the c:\ drive: PS /home/username>

问题 I have an ASP.NET Core 3.1 based app. During the app startup, in the ConfigureServices(IServiceCollection services) I want to register my services. But during configuring services, I want to boot the app based on settings found in the database. Here is my code public void ConfigureServices(IServiceCollection services) { // Register context services.AddDbContext<AppDbContext>(options => { options.UseMySql(Configuration.GetConnectionString("MySqlServerConnection")); }); // Reister the setting

问题 After upgrading a project from ASP.NET Core 3.0 to ASP.NET Core 3.1 , my application stopped working on Azure App Services —but only when published using continuous deployment from Azure DevOps Pipelines . (Similar to another question, it continues to work if I publish directly from Visual Studio.) Specifically, the pipeline is still able to publish using the Azure App Service Deploy ( AzureRmWebAppDeployment ) task, but it fails to load in the Azure App Service environment with a 500.32

问题 After upgrading a project from ASP.NET Core 3.0 to ASP.NET Core 3.1 , my application stopped working on Azure App Services —but only when published using continuous deployment from Azure DevOps Pipelines . (Similar to another question, it continues to work if I publish directly from Visual Studio.) Specifically, the pipeline is still able to publish using the Azure App Service Deploy ( AzureRmWebAppDeployment ) task, but it fails to load in the Azure App Service environment with a 500.32

问题 I've seen basically the same question answered for net core 2.2 on ASP Net Forum. When I tried to implement for my net core 3.1 application, I'm getting an error System.InvalidCastException: Unable to cast object of type 'System.Security.Claims.ClaimsIdentity' to type 'System.Security.Principal.WindowsIdentity' The error happens on the RoleAuthHandler.cs trying to cast Identity to WindowsIdentity. I'm wondering if there has been change between core 2.2 and 3.1 that explains this or I'm doing