Wrappers for [Initialize/Update]ProcThreadAttributeList & CreateProcess #15
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.
Initial draft for providing wrappers for
InitializeProcThreadAttributeList
,InitializeProcThreadAttributeList
andCreateProcess
.DeleteProcThreadAttributeList
to follow.Feedback welcome - particularly interested in your option on issues like:
https://github.com/rasta-mouse/DInvoke/blob/dev/DInvoke/DInvoke/DynamicInvoke/Win32.cs#L117-L120
I've currently abstracted
SECURITY_ATTRIBUTES
away from the user, as I feel most use cases would not have a need to change them. But should we not do that? Should they be optional overloads?Changes can be tested with the following: