-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Upgrade Microsoft.NETCore.UniversalWindowsPlatform #9194
Labels
Area: Infrastructure
enhancement
PR Follow-up
Issue created in response to PR Feedback (labeled so we can gather telemetry on follow-up)
Milestone
Comments
@AgneLukoseviciute there likely are side effects with .NET Native and other things, right? Any idea how disruptive this will be? When should we tackle this? |
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this issue
Nov 5, 2024
This PR backports microsoft#14084 to 0.76. ## Description This PR upgrades the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why This is long over-due as the latest (and probably last) version of this package hasn't changed in over two years. There's no reason for us to build against an older version. Just as importantly, this brings in a newer version of the .NetNative toolchain, which seems to resolve issues around C# builds hanging at the .NetNative step. Resolves microsoft#14055 Resolves microsoft#9194 Resolves microsoft#4869 ### What Updated the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. Added new entries to the props that enable C++ apps to consume C# modules to see the latest versions of .NetNative. ## Screenshots N/A ## Testing Verified E2Etests build and run. ## Changelog Should this change be included in the release notes: _yes_ Update to Microsoft.NETCore.UniversalWindowsPlatform 6.2.14
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this issue
Nov 5, 2024
This PR backports microsoft#14084 to 0.75. ## Description This PR upgrades the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why This is long over-due as the latest (and probably last) version of this package hasn't changed in over two years. There's no reason for us to build against an older version. Just as importantly, this brings in a newer version of the .NetNative toolchain, which seems to resolve issues around C# builds hanging at the .NetNative step. Resolves microsoft#14055 Resolves microsoft#9194 Resolves microsoft#4869 ### What Updated the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. Added new entries to the props that enable C++ apps to consume C# modules to see the latest versions of .NetNative. ## Screenshots N/A ## Testing Verified E2Etests build and run. ## Changelog Should this change be included in the release notes: _yes_ Update to Microsoft.NETCore.UniversalWindowsPlatform 6.2.14
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this issue
Nov 5, 2024
This PR backports microsoft#14084 to 0.74. ## Description This PR upgrades the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why This is long over-due as the latest (and probably last) version of this package hasn't changed in over two years. There's no reason for us to build against an older version. Just as importantly, this brings in a newer version of the .NetNative toolchain, which seems to resolve issues around C# builds hanging at the .NetNative step. Resolves microsoft#14055 Resolves microsoft#9194 Resolves microsoft#4869 ### What Updated the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. Added new entries to the props that enable C++ apps to consume C# modules to see the latest versions of .NetNative. ## Screenshots N/A ## Testing Verified E2Etests build and run. ## Changelog Should this change be included in the release notes: _yes_ Update to Microsoft.NETCore.UniversalWindowsPlatform 6.2.14
jonthysell
added a commit
that referenced
this issue
Nov 5, 2024
…14087) This PR backports #14084 to 0.74. ## Description This PR upgrades the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why This is long over-due as the latest (and probably last) version of this package hasn't changed in over two years. There's no reason for us to build against an older version. Just as importantly, this brings in a newer version of the .NetNative toolchain, which seems to resolve issues around C# builds hanging at the .NetNative step. Resolves #14055 Resolves #9194 Resolves #4869 ### What Updated the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. Added new entries to the props that enable C++ apps to consume C# modules to see the latest versions of .NetNative. ## Screenshots N/A ## Testing Verified E2Etests build and run. ## Changelog Should this change be included in the release notes: _yes_ Update to Microsoft.NETCore.UniversalWindowsPlatform 6.2.14
jonthysell
added a commit
that referenced
this issue
Nov 6, 2024
…14085) This PR backports #14084 to 0.76. ## Description This PR upgrades the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why This is long over-due as the latest (and probably last) version of this package hasn't changed in over two years. There's no reason for us to build against an older version. Just as importantly, this brings in a newer version of the .NetNative toolchain, which seems to resolve issues around C# builds hanging at the .NetNative step. Resolves #14055 Resolves #9194 Resolves #4869 ### What Updated the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. Added new entries to the props that enable C++ apps to consume C# modules to see the latest versions of .NetNative. ## Screenshots N/A ## Testing Verified E2Etests build and run. ## Changelog Should this change be included in the release notes: _yes_ Update to Microsoft.NETCore.UniversalWindowsPlatform 6.2.14
jonthysell
added a commit
that referenced
this issue
Nov 6, 2024
…14086) This PR backports #14084 to 0.75. ## Description This PR upgrades the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why This is long over-due as the latest (and probably last) version of this package hasn't changed in over two years. There's no reason for us to build against an older version. Just as importantly, this brings in a newer version of the .NetNative toolchain, which seems to resolve issues around C# builds hanging at the .NetNative step. Resolves #14055 Resolves #9194 Resolves #4869 ### What Updated the minimum version of `Microsoft.NETCore.UniversalWindowsPlatform` to 6.2.14 for UWP C# projects. Added new entries to the props that enable C++ apps to consume C# modules to see the latest versions of .NetNative. ## Screenshots N/A ## Testing Verified E2Etests build and run. ## Changelog Should this change be included in the release notes: _yes_ Update to Microsoft.NETCore.UniversalWindowsPlatform 6.2.14
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: Infrastructure
enhancement
PR Follow-up
Issue created in response to PR Feedback (labeled so we can gather telemetry on follow-up)
We upgraded to 6.2.9 in May, 2020 - might be a good idea to upgrade to 6.2.13 to get current.
Originally posted by @asklar in #9177 (comment) in reference to the Upgrade Microsoft.NETCore.UniversalWindowsPlatform version.
The text was updated successfully, but these errors were encountered: