Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide a dotnet global tool version of ilrepack #364

Merged
merged 7 commits into from
Jul 26, 2024
Merged

Provide a dotnet global tool version of ilrepack #364

merged 7 commits into from
Jul 26, 2024

Commits on Jul 8, 2024

  1. Create ILRepack dotnet-tool for simpler distribution

    @kzu
    kzu committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    701f865 View commit details
    Browse the repository at this point in the history

  2. Add GitHub workflows to pack install and publish tool 

    * Automatically version from github.ref
* Build and test on windows, only sanity check run on others
* Build using desktop MSBuild: This is what appveyor does.
* Pack separately just the tools project.
    @kzu
    kzu committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    c49dc08 View commit details
    Browse the repository at this point in the history

  3. Bump dependencies so they restore properly for tests

    @kzu
    kzu committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    7a07939 View commit details
    Browse the repository at this point in the history

  4. Add --version to quickly render tool version 

    This command also helps check the tool is installed properly and can run, returning a success status code, without having to repack anything actually.
    @kzu
    kzu committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    2f7ad3f View commit details
    Browse the repository at this point in the history

  5. Make .vs folder ignoring recursive 

    Avoids having to skip it for the auto-generated .vs when you open a single project from the integration tests folder, for example
    @kzu
    kzu committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    6e1a1c1 View commit details
    Browse the repository at this point in the history

  6. Add a sample analyzer project with dependencies to sanity-check 

    In order to test that the basics of the dotnet-ilrepack tool are working in all supported OSes, we pick a clean and common scenario that doesn't require any particular workload, and which builds fast, as a simple end-to-end sanity check for the global tool itself.

Note that the extensive tests already run on the code from existing tests is a prerequisite already for the test tool job.
    @kzu
    kzu committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    561c39a View commit details
    Browse the repository at this point in the history

  7. Pack and publish selectively depending on secrets 

    This makes merging this PR to upstream can be done even if the GH workflows aren't used for publishing.
    @kzu
    kzu committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    ab66d9c View commit details
    Browse the repository at this point in the history