Read container ID from event extended data #125
Merged
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
swannman
requested changes
Apr 15, 2020
swannman
requested changes
Apr 18, 2020
swannman
requested changes
Apr 20, 2020
added 6 commits
April 20, 2020 15:29
a002c06 to
89f1a48
Compare
|
Force push was a rebase to pull in the changes from the previous PR. |
swannman
approved these changes
Apr 20, 2020
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.
This change should allow reading Windows container ID's from events coming from both Provider and RawProvider (from the managed API).
There's an extra #ifdef in extended_data_builder.hpp for compatibility with Windows SDK version 10.0.18362.0.
I will add nuspec version changes once it's clear what the version number should be.