nopCommerce 4.00 BETA released. Please share your impressions

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.00 and share your feedback with us.

In this version, our development efforts were focused on moving nopCommerce to ASP.NET Core 2.0, performance and architecture improvements, further enhancements, and bug fixing. The highlights for this version:

•  Migration to ASP.NET Core 2.0. Please note that we target .NET Framework 4.6.1 and not .NET Core. We plan to use .NET Core only when EF Core team starts supporting all ORM functionality from the classic Entity Framework 6. Such as lazy loading, etc (they plan to do it in Q1-Q2 2018).
•  Significant performance enhancements. It’s not just about migration to ASP.NET Core. We’ve made many other changes to increase performance

The release notes don’t include all changes caused by migration to ASP.NET Core. Here is a separate upgrade guide for developers on how to migrate existing projects and plugins to this version because the number of changes is really HUGE! You can find the full release notes here.

In order to download nopCommerce 4.00 BETA please use the following links:
BETA 4.00 - Source code (download if you are a web developer interested in the nopCommerce application source code)
BETA 4.00 - No source code (download this package if you want to deploy a live site to a web server with the minimum required files)
Upgrade script from 3.90 (download this package to upgrade an existing installation to a newer version)

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!

Dear Andrei
As you Told "we target .NET Framework 4.6.1 and not .NET Core" So can we publish it to Linux instead of Windows?

Great Work!

Testing it out as we speek :)

Way to go, Andrei!

nopCommerce 4.0 will be an awesome release!

Just a small comment on the above.
If you plan to release the official version in 2-3 weeks and release the developer upgrade guide in about a week this means that nopCommerce developers will have only 1-2 weeks to upgrade their extensions, which I believe is a very short period of time.

Please don't get me wrong as we started with the upgrade 2 months ago (which is quite hard with the many changes you did in the last couple of weeks). But in order to convince more and more people to upgrade to the new version then there must be at least some extensions available for it several days after the official release. I don't think that many of the nopCommerce vendors will be able to upgrade and test all their products on time and release their extensions a few days after the official release. We should target code freeze and BETA releases at least 3-4 weeks before the official release next time (especially after such a big release that has a lot of changes).
This is just a constructive comment to make the nopCommerce ecosystem much more stable and provide more confidence in the nopCommerce community.

p.s: There are no bugs in nopCommerce 4.0 ;)

Thanks,
Boyko

sumit7034 wrote:
No. Only .NET Core is multi-platform. We'll support Linux only when start using .NET Core (most probably in the next version)

Nop-Templates.com wrote:
We'll do our best to publish it earlier

Nop-Templates.com wrote:

+1

Looks so great.
Can´t wait to go live with 4.00 :-)

Nop-Templates.com wrote:

Way to go Andrei.

And I agree with what Boyko has said. We should have code freeze and beta releases at least 3-4 weeks before the official release.. +1

I have following problems with 4.0 BETA on Server compact running on VS2017 community, rebuild just out of the box:

After installation completed VS goes to stop(no warning or messages).
Click on reload plugin list, VS goes to stop(no warning or messages).
click on uninstall a random plugin, VS goes to stop(no warning or messages).

I will test on my test SQL DB now and see if it´s just the compact giving these problems.