Reference the "Riverside.Win32" Win32 metadata projection in README.md #2093
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi!
I've recently been working on a little project, simply titled 'Riverside.Win32', that uses some tricks to generate Win32 methods/structs/enums/etc. from the Win32 metadata (this repo!) that work across .NET (rather than using the generator approach CsWin32 uses, this makes all code completely static and available over an array of packages that are specific to each Win32 library it is built from).
Having a strong Win32 PInvoke binding for all .NET languages, including VB.NET, F#, IronPython, C++/CLI and others is a much wanted product however CsWin32, being a source generator, is only capable of building generations for one language: C#.
So, I created the Riverside.Win32 project, which creates bindings from the Win32 metadata via CsWin32 and publishes it to NuGet for extreme ease-of-use.
It would be nice to get a little recognition for it since I've seen many ask for this kind of package before, with little answer.
Thanks!