Note that this property completely disables a native executable being created for the project during build, not just in the context of launching the project via dotnet run. To workaround this issue the MSBuild property can be set in the project file to false, e.g.: Note the issue doesn't occur when launching via Visual Studio for Mac 2022 as it doesn't use dotnet run to launch the app. support for cross-architecture app launching, the process name being the project name, etc.) it results in every new project being a new executable from the OS's security point-of-view, and thus requires each new web app to explicitly be granted access to the Keychain. NET 6 dotnet run was changed to launch the app via the AppHost executable rather than via dotnet MyApp.dll. MacOS prompt showing message "Host6 wants to access key "tmpE4viKq" in your keychain."Ī textbox for the password and three buttons are also shown: Always Allow, Deny, Allow. This process must be repeated for every new ASP.NET Core project created. After entering their password and clicking "Allow" or "Always Allow" the app starts. When using dotnet run on a newly created ASP.NET Core project on MacOS, the user is prompted by the OS to allow access to the Keychain so that the app can access the HTTPS developer certificate.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |