-
Notifications
You must be signed in to change notification settings - Fork 77
Add support for .NET 10 #476
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
base: main
Are you sure you want to change the base?
Changes from all commits
05a7387
b216f6b
724af5d
693e567
77de97d
e44aac1
c3d40c3
afb7d98
a638a08
5b1187b
c3f520a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,8 +1,7 @@ | ||
| # DO NOT SPECIFY AUTHENTICATION CREDENTIALS IN THIS FILE. | ||
| # It should only be used to configure NPM registry sources. | ||
|
|
||
| # Use ADO public NPM registry to be complient | ||
| # Use ADO public NPM registry to be compliant | ||
| # Additional registries should be added as upstreams instead of being added here. | ||
|
|
||
| registry=https://pkgs.dev.azure.com/ms/react-native/_packaging/react-native-public/npm/registry/ | ||
| always-auth=true | ||
| registry=https://pkgs.dev.azure.com/ms/react-native/_packaging/react-native-public/npm/registry/ | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -46,7 +46,7 @@ | |
| "-c", | ||
| "Release", | ||
| "-f", | ||
| "net9.0", | ||
| "net10.0", | ||
| "--", | ||
| "--filter", | ||
| "*.NonAot.*" | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -86,7 +86,7 @@ For a minimal example of this scenario, see | |
| const dotnet = require('node-api-dotnet/net8.0'); | ||
| ``` | ||
| ::: | ||
| Currently the supported target frameworks are `net472`, `net8.0`, and `net9.0`. | ||
| Currently the supported target frameworks are `net472`, `net8.0`, `net9.0`, and `net10.0`. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The comment says that we support net9.0, but I see it being removed from the build matrix in the pipelines.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Where in the build matrix that net9.0 was removed? Could you point out the file. There're a few places where we build the project with the latest framework, so I replaced .net 9 with .net 10. But other than those, I just added the new net10 to the build matrix.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am referring to the
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am OK with that. There are probably few if any teams on .NET 9 who haven't already migrated to .NET 10. So it's OK to exclude 9 from the build matrix until support is dropped. (Official support for .NET 9 ends Nov 2026.) Anyway it is very unlikely that there would be any bug on .NET 9 that doesn't also repro on either 8 or 10.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh, it looks like in publish.yml both .NET 9 and 10 are published for Windows
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yep, I am for consistency. If we want to drop 9.0 then it is fine. Let's just make it consistent through the code. Though, I would rather keep 9.0 at least until the end of the official .Net support.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @vmoroz @jasongin With the current code, I saw that on windows we built net8, net9 and net47, but only built the latest net9 on macos and linux. So I thought for those two platforms, I just needed to replace net9 and net10. I'm happy to add net9 back for macos and linux. Let me know what you think? What's the reason we don't build net8 on those platforms?
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I added .net9 back for macos and linux |
||
|
|
||
| 7. Load your .NET module assembly from its path using the `dotnet.require()` function: | ||
| ```JavaScript | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.