Simplify dotnet publish and update project config #21
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.
Refactored the GitHub Actions workflow to use a more streamlined dotnet publish command by referencing predefined publish profiles. This change introduces Default and Aot publishing profiles that centralize common publishing settings and provide a foundation for future publishing scenario diversifications. By leveraging publish profiles, we ensure consistency across our build and release pipelines, while also making the process more maintainable.
In the csproj file, we've refined the project configuration by organizing property groups and incorporating
UseRidGraph
, preparing for potential platform identifier transitions by external dependencies like Yubico. The.gitignore
modification clarifies our stance on keeping.pubxml
files version-controlled unless they contain sensitive information.The addition of
Common.props
,Aot.pubxml
, andDefault.pubxml
under the PublishProfiles directory encapsulates shared properties and specific configurations for Ahead-of-Time compilation and default publishing scenarios, respectively. This setup paves the way for more targeted build optimizations and aligns with best practices for .NET application deployment.These changes collectively aim to enhance the build efficiency, clarity in project settings, and adaptability to future .NET platform evolutions.