Dear nopCommerce community!
The new version of nopCommerce is about to be released. But before we announce it officially, we want you to BETA test the upcoming nopCommerce 4.50.0 and share your feedback with us.
We've migrated nopCommerce to .NET 6 (the latest available version of .NET platform). No
other major features have been introduced with this release as our development efforts were
focused on architecture improvements, source code refactoring, further enhancements and fixing
bugs. Please find release notes here and all closed work items here.
Download. In order to download nopCommerce 4.50 BETA please use the following links:
BETA 4.50 - Source code (download this package with source code if you are a web developer planning to customize nopCommerce.)
BETA 4.50 - No source code (download this package if you want to quickly deploy your site to a web server.)
Requirements. Please note that nopCommerce 4.50 requires Visual Studio 2022 (17.0.0) or above, .NET 6 SDK
(6.0.100) (download), and ASP.NET Core Runtime (v6.0.0) - Windows Hosting Bundle
(download).
P.S. You can download .NET 6 SDK and ASP.NET Core Runtime 6.0.0 for other operating systems (e.g. Linux, macOS, Windows) and families of processors (e.g. Arm64, x64. x86) here.
Upgrade instructions. If you're upgrading nopCommerce to version 4.50 from one of the previous versions, please
ensure that your connection string contains one of the following parameters: "Encrypt=false" or
"TrustServerCertificate=True" (depending on your server requirements). You can manually add
these parameters to your connection string in the \App_Data\appsettings.json file. This step is
caused by the "Microsoft.Data.SqlClient" library that changed the default value of the "Encrypt"
option from "false" to "true".
Bug bounty. We'd love if developers could get involved with testing to find any issues which will need fixing before the final release. Please share your thought after testing in this forum topic. Please also learn more about our BETA testing program here (earn $10 for each reported bug). Thank you!
