-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Enable the CLI to create a C++/WinRT native module library that consumes Microsoft.ReactNative #3203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Stretch goal for M3, possibly move to M4. |
This sounds super awesome! We currently have about 15 native packages/modules inside our main app's project and would love an easier time creating new libraries for each one and pull them out properly. |
Potentially considering putting this in @brodybits/create-react-native-module, rather than our own CLI. |
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this issue
Sep 11, 2020
This PR extends `react-native-windows-init` with a `--projectType [app|lib]` option and a set of new native module lib templates for both C++ and C#. This provides a much needed mechanism for developers wishing to add windows implementation to an existing native module (esp. community modules) without having to set up the VS files manually. Closes microsoft#3203 Closes microsoft#3201
jonthysell
added a commit
that referenced
this issue
Sep 18, 2020
…5921) This PR extends `react-native-windows-init` with a `--projectType [app|lib]` option and a set of new native module lib templates for both C++ and C#. This provides a much needed mechanism for developers wishing to add windows implementation to an existing native module (esp. community modules) without having to set up the VS files manually. Closes #3203 Closes #3201
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Project should be set up similar to the SampleLibraryCPP sample:
The text was updated successfully, but these errors were encountered: