Upgrading to Virto Commerce on .NET 6
Introduction
This document will guide you through updating VC Platform Manager and VC modules to version 3.200 or higher based on .NET 6.
Prior to Update
Before you start running your update, please review .NET 6 Release Notes.
Breaking Change Note
As Microsoft introduced some breaking changes into Entity Framework, as well as for some other reasons, VC modules are imcompatible with the Platform having a different version, and vice versa. Technically, VC Platform version 3.200 or higher cannot load and manage VC modules with any version below 3.200, and the other way round. For the above reasons, there is no option for partial update, which means you have to update your entire project to .NET 6.
Developer Experience
Make sure both .NET 6 SDK and Visual Studio 2022 have been installed to your environment.
VC Build Tool
After update to Virto Commerce on .NET 6, please use this vc-build version: virtocommerce.globaltool 3.0.0.
dotnet tool install --global VirtoCommerce.GlobalTool --version 3.0.0
List of Releases
| # | Name | Link |
|---|---|---|
| 1 | VC Platform | 3.200 |
| 2 | VC Google ecommerce analytics | 3.200 |
| 3 | VC Assets | 3.200 |
| 4 | VC Notifications | 3.200 |
| 5 | VC Core | 3.200 |
| 6 | VC Export | 3.200 |
| 7 | VC Search | 3.200 |
| 8 | VC Store | 3.200 |
| 9 | VC XApi profile | 3.200 |
| 10 | VC Authorize.Net | 3.200 |
| 11 | VC Avalara | 3.200 |
| 12 | VC Azure search | 3.200 |
| 13 | VC Catalog CSV import | 3.200 |
| 14 | VC Catalog personalization | 3.200 |
| 15 | VC Catalog publishing | 3.200 |
| 16 | VC Dynamic associations | 3.200 |
| 17 | VC Elastic search | 3.200 |
| 18 | VC Image tools | 3.200 |
| 19 | VC Lucene search | 3.200 |
| 20 | VC Catalog | 3.200 |
| 21 | VC Pricing | 3.200 |
| 22 | VC Shipping | 3.200 |
| 23 | VC Payment | 3.200 |
| 24 | VC Cart | 3.200 |
| 25 | VC Inventory | 3.200 |
| 26 | VC Customer | 3.200 |
| 27 | VC Orders | 3.200 |
| 28 | VC File system assets | 3.200 |
| 29 | VC Azure blob assets | 3.200 |
| 30 | VC Marketing | 3.200 |
| 31 | VC Content | 3.200 |
| 32 | VC Tax | 3.200 |
| 33 | VC XApi | 3.200 |
| 34 | VC WebHooks | 3.200 |
| 35 | VC Subscription | 3.200 |
| 36 | VC Sitemaps | 3.200 |
| 37 | VC Bulk actions | 3.200 |
| 38 | VC Quote | 3.200 |
| 39 | VC Customer review | 3.200 |
FAQs
How can I migrate my custom/extension module?
- Make sure all required prerequisites, such as VS 2022 and .NET 6 SDK, have been installed to your environment.
- Open project properties and change Target Framework to .NET 6.0.
<TargetFramework>net6.0</TargetFramework> - Update All Microsoft and Entity Framework dependencies to 6.0.0.
- Bump all dependent VirtoCommerce NuGet packages to at least version 3.200.
- Fix all issues and make sure the solution gets compiled and load successfully.
Please note: When the developing and debugging processes are running, do not compile your module with .NET Core 3.1 and .NET 6 at the same time.
Slow performing database migrations
In some cases, DB migration might take long time and throw an timeout exceptions. You can deal with it by using vc-build tool and following the tips described in this guide or here or even here.