-
Notifications
You must be signed in to change notification settings - Fork 12
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
Find a way to publish a single-file dll for the powershell modules #90
Comments
Do you have to use Powershell? Is there a specific example you can share? |
Ah.. the context is a bit cryptic here since it was mainly a note-to-self.... This concerns the way the edit-kql powershell module is built. It's compiled as a powershell cmdlet into a dll called "pskql.dll". The building is done (for publishing) via the build.ps1 script. You'lll notice a few lines further down there is an attempt to remove the framework dlls from the distributed set which ends up in publish\pskql folder There are sevveral annoying things about this:
|
It's probably possible to create a self-contained pskql using ILMERGE but atm it seems likely that the net9/powershell incompatibitly will be fixed before I have time to wrestle with that. |
Is the issue that you ultimately need to: "allow objects to be piped into a KustoLoco table and queried."?
In my project I only allow you to bring in data using: |
Ohh yeah I don't use terminal at all. |
It's very frustrating that the powershell modules need to be published as a rather random collection of dlls. This has already caused problems with installations failing as environments and net verisons change.
Unfortunately the -self-contained flag seems to be ignored when publishing dlls.
The text was updated successfully, but these errors were encountered: