Prefer dnx for CLI usage#78
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the README, package readme, and built-in CLI help text to prefer
.NET 10dnx DiagramForge.Tool ...usage over installed-tool command examples.What changed
README.mdCLI install/usage examples to usednx DiagramForge.Tool ...doc/PackageReadme.mdCLI install/usage examples to usednx DiagramForge.Tool ...src/DiagramForge.Cli/Program.cshelp output examples to match the same guidanceWhy
Since DiagramForge targets
.NET 10, the preferred way to run the tool is viadnx DiagramForge.Tool ...without requiring a prior global tool install. This keeps the docs and help text aligned with the recommended workflow.Validation