Fix: Add-Type exceptions during runtime compilation #283
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LordHepipud
changed the title
LordHepipud
force-pushed
the
fix/add_type_exceptions
branch
from
9cfb498 to
64ceb81
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Icinga for Windows is using Add-Type in some small cases, to properly fetch UNC Path values for plugins or disk attribute information.
While in most cases this works without problems, sometimes the on-the-fly compilation fails because of out-of-memory exceptions or different errors.
This fix will now compile the DLL required inside the cache/dll folder if not present and load the compiled DLL's if required and available by using the new Framework function
Add-IcingaAddTypeLib