Hi Daryl,

When starting an ASP.NET Core project, It's recommened to trust the HTTPS development certificate. Refer to ASP.NET document:

https://docs.microsoft.com/aspnet/core/getting-started/?view=aspnetcore-2.1&tabs=windows#trust-the-development-certificate

https://docs.microsoft.com/aspnet/core/security/enforcing-ssl?view=aspnetcore-2.1&tabs=visual-studio#trust-the-aspnet-core-https-development-certificate-on-windows-and-macos

You can also manage HTTPS development certificates by dotnet dev-certs command line.

Usage: dotnet dev-certs https [options]

Options:
-ep|--export-path Full path to the exported certificate
-p|--password Password to use when exporting the certificate with the private key into a pfx file
-c|--check Check for the existence of the certificate but do not perform any action
--clean Cleans all HTTPS development certificates from the machine.
-t|--trust Trust the certificate on the current platform
-v|--verbose Display more debug information.
-q|--quiet Display warnings and errors only.
-h|--help Show help information

When you don't want to trust trust the HTTPS development certificate, there should be an option in this dialog to prevent this message from showing again. You can report a SnapDevelop enhancement requestment in the Appeon Standard Support at https://www.appeon.com/standardsupport/.

Regards,
Logan