Skip to content

VCST-4328: Update to .NET10#159

Merged
OlegoO merged 3 commits intodevfrom
feat/VCST-4328-net10
Feb 12, 2026
Merged

VCST-4328: Update to .NET10#159
OlegoO merged 3 commits intodevfrom
feat/VCST-4328-net10

Conversation

@OlegoO
Copy link
Contributor

@OlegoO OlegoO commented Feb 12, 2026

Description

Update to .NET10

References

QA-test:

Jira-link:

https://virtocommerce.atlassian.net/browse/VCST-4328

Artifact URL:

https://vc3prerelease.blob.core.windows.net/packages/VirtoCommerce.Inventory_3.1000.0-pr-159-5504.zip


Note

Medium Risk
Framework and dependency upgrades can introduce build/runtime and test runner incompatibilities (including EF tooling and xUnit v3 migration), though changes are largely configuration/package-level.

Overview
Upgrades the Inventory module to .NET 10 by retargeting all projects (Core, Data, DB providers, Web, and tests) from net8.0 to net10.0 and bumping the module version to 3.1000.0.

Aligns dependencies with the new platform line: updates VirtoCommerce package references (Platform/Core/Search/Catalog dependencies in module.manifest) to 3.1000.x, updates EF tooling/design packages to 10.0.1, adds NU1608 suppression where needed, and refreshes the web package-lock.json (notably webpack and related transitive packages).

Written by Cursor Bugbot for commit 0da06fd. This will update automatically on new commits. Configure here.

@sonarqubecloud
Copy link

@OlegoO OlegoO merged commit b4e7f8d into dev Feb 12, 2026
5 of 6 checks passed
@OlegoO OlegoO deleted the feat/VCST-4328-net10 branch February 12, 2026 16:39
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

<TargetFramework>net10.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
<NoWarn>NU1608</NoWarn>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suppressed dependency conflict warnings hide incompatibilities

Medium Severity

Adding NU1608 to NoWarn in multiple projects suppresses package constraint conflict diagnostics instead of resolving them. That allows restore/build to proceed with potentially incompatible dependency graphs, which can surface later as runtime behavior changes, EF tooling failures, or unstable test execution after the .NET 10 upgrade.

Additional Locations (2)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant