Skip to content

Conversation

danmoseley
Copy link
Member

I noticed it creates one if not present (eg., you did --clean) but the help message did not show how to create one.

@ghost ghost added the area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI label Feb 1, 2025
@danmoseley danmoseley requested a review from javiercn February 1, 2025 05:21
@danmoseley
Copy link
Member Author

Well, actually "dotnet dev-certs https" alone will create one if necessary (but untrusted).. Not sure where I'd put that. This change is accurate and an improvement. The actual docs explain all.

@adityamandaleeka
Copy link
Member

Note that when --check is also used with --trust it will just bail if there's no existing cert.

@danmoseley
Copy link
Member Author

updated, now looks like this:

Usage: dotnet dev-certs https [options]

Options:
...
  --format           Export the certificate in the given format. Valid values are Pfx and Pem. Pfx is the default.
  -t|--trust         When not combined with the --check option, trusts the certificate on the current platform, creating one if necessary.
                     When combined with the --check option, validates that there is a certificate and it is trusted.
  -v|--verbose       Display more debug information.
...

@danmoseley
Copy link
Member Author

@adityamandaleeka ok ?

@adityamandaleeka adityamandaleeka merged commit 77b7aaf into dotnet:main Feb 19, 2025
27 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the 10.0-preview2 milestone Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants