Skip to content
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

Minor edits to slide deck #172

Merged
merged 1 commit into from
Nov 9, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions Docs/presentation2.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ While some limited solutions exist, there are opportunities to do better in many
---
## Primary .NET / JS Interop scenarios
- Dynamically invoke .NET APIs from JS.
- Develop Node.js addon modules in C#.
- Develop Node.js addon modules in C# (runtime-dependent or Native AOT).
- Host a JS runtime within a .NET app and call JS APIs from .NET.
- Develop React Native apps and extensions in C# with JS interop.

Expand Down Expand Up @@ -220,18 +220,19 @@ Numbers are _microseconds_. "Warm" is an average of 10000 .NET -> JS calls (pass

---
## Project status
- Available for early experimentation
- Currently in public preview
- Send feedback, bug reports to [microsoft/node-api-dotnet/issues](https://github.com/microsoft/node-api-dotnet/issues)
- Help prioritize areas for improvement.
- Contribute PRs!
- Current limitations may block some advanced interop scenarios.
- NOT production ready

---
## Roadmap
Major development areas:
- More marshalling: events, generics, ...
- Add support for extension methods, .NET events, better overload resolution
- Custom marshalling
- API review / refinement
- More test coverage
- Explore interop with WinRT, WASM

Project backlog: https://github.com/orgs/microsoft/projects/779