nullFilter: VS2022 compatibility and best practices by default #999
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.
I have been building Minifilter driver lately and was supriced how much issues there are on existing samples and challenges which developers have faced because of it (there is multiple issues because of it in here and other forums).
This PR updates nullFilter sample in way that:
ntstrsafe.h
is used instead ofdontuse.h
. This driver actually don't need that at all but as this is sample it is good idea to share correct way on it.In addition that this provides better starting point for developers, I did find it also useful to verify that my HLK Client machines are working correctly as cases like File IO 2 Tests needs very special configuration.