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.

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

Ensure that Eazfuscator.NET is installed and sourced correctly as part of the build #184

Open
2 tasks done
gep13 opened this issue Feb 18, 2025 · 0 comments
Open
2 tasks done

Comments

@gep13
Copy link
Member

gep13 commented Feb 18, 2025

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

Currently, adding build assemblies into the lib folder of the repository is problematic for a couple of reasons.

  1. It adds bloat to the size of the repository
  2. Makes it "hard" to update the assemblies, as it needs to be done in multiple places
  3. Makes it "easy" to become inconsistent in terms of what version of the application is used across multiple repositories.

Describe The Solution. Why is it needed?

Currently, we rely on the Eazfuscator.NET.exe being added to the lib folder of the repository where it is required. Instead, we should source the installer for Eazfuscator.NET.exe, and ensure that it is installed on the machine where the build is being performed. This can either be done via the settings.kts file for the project, or by adding the installation of the Eazfuscator package to the overall build, using the Chocolatey Module for Cake. The latter seems more applicable, this is means that the requirement is "closer" to the build itself. However, we don't want/need, all projects that use Chocolatey.Cake.Recipe to install Eazfuscator, as this is not always required. Instead, create a build parameter, defaulting to false, that performs the installation when required.

Additional Context

N/A

Related Issues

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant