Add information about how to reverse engineer COM interfaces #97
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 PR adds a "note" markdown file to the repository with information about how to find COM interface ids and function definitions. It also includes a Rust CLI program that automatically gathers all that information and prints it to stdout.
I was myself curious how this information was gathered and I don't think I am alone considering: #93 (comment) and #94.
The reason that the CLI tool is in a different workspace is so that you don't need to download or compile its dependencies when building the main project.
This work was largely started because of the information provided in issue #14 ("Reverse engineering process") on the C# library Slion/VirtualDesktop. It linked to the Python script mzomparelli/GetVirtualDesktopAPI_DIA which inspired the initial Rust CLI program.