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

Allow alternative plugin directory #12

Open
janssen-io opened this issue Aug 21, 2024 · 0 comments
Open

Allow alternative plugin directory #12

janssen-io opened this issue Aug 21, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@janssen-io
Copy link
Owner

Since I've started versioning assemblies and plugins are always loaded from the same directory, debugging a development build can be troublesome. The published plugin expects a specific version of the TransactionQL.Input assembly, which of course is not available in the development build directory.

Originally posted by @janssen-io in #7 (comment)

Possible fix is to set an alternative plugin directory. Initially via command line arguments, but it could also just be a setting in the About-window.

@janssen-io janssen-io added the enhancement New feature or request label Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant