nopCommerce 4.00 roadmap and estimated release date. Let's discuss

3 years ago
Timely solution!
An ASP.NET Core app can use the .NET Core or .NET Framework runtime.
Which runtime do you plan to use?
3 years ago
robbyr wrote:
How to update 3.9 to 4.0?

The upgrade process will be almost same as from any other version (e.g. from 3.80 to 3.90)

robbyr wrote:
Are you guys rewriting complete NOP again?
...
All logics are changing in CORE?

No. Business logic will stay absolutely the same. Controller logic will also be the same. Markup will be the same (almost). Etc, etc. Actually not much changes (not like we did when moving from 1.90 to 2.00). I think we'll come with more details in several weeks. As for now I can only recommend to have a look at articles at https://docs.microsoft.com/en-us/aspnet/core/migration/ to get an idea on what could be changed
3 years ago
ASP.NET Core provides new capabilities for building multi-tenant applications.
One approach is described in the article http://benfoster.io/blog/asp-net-5-multitenancy
3 years ago
Hey Andrei,

Can you please give us the option to choose MySQL or PostgreSQL?  I believe after this NopCommerce will be fully cross platform and will be number 1 very soon :)

Thanks,
PS
3 years ago
Andrei,

please include the possibility to have a separated admin site instead inside /admin path, this simple "security trick"
can help a lot and avoid problems.

BTW, it is possible already, but not out of the box, we have to duplicate DLLs beside another changes.

Thanks!
3 years ago
i think this functions very important and need to set Milestone 4.0

https://github.com/nopSolutions/nopCommerce/issues/276
https://github.com/nopSolutions/nopCommerce/issues/2148
https://github.com/nopSolutions/nopCommerce/issues/2191
https://github.com/nopSolutions/nopCommerce/issues/2219
https://github.com/nopSolutions/nopCommerce/issues/2229
https://github.com/nopSolutions/nopCommerce/issues/2236
https://github.com/nopSolutions/nopCommerce/issues/2241
https://github.com/nopSolutions/nopCommerce/issues/2244
https://github.com/nopSolutions/nopCommerce/issues/2248
https://github.com/nopSolutions/nopCommerce/issues/2251
https://github.com/nopSolutions/nopCommerce/issues/2253
https://github.com/nopSolutions/nopCommerce/issues/2257
https://github.com/nopSolutions/nopCommerce/issues/1768
https://github.com/nopSolutions/nopCommerce/issues/2047  (import/export Specification Attributes)
https://github.com/nopSolutions/nopCommerce/issues/2079
https://github.com/nopSolutions/nopCommerce/issues/2080
3 years ago
What about fixing the DB access and making all operations async? The nop team should look at this topic and take action.

Also, the architecture needs to be reviewed. It is not normal having controllers with 20 services injected in the constructor and in their turn, the services having 20 more services injected in their constructors. Also, many controller actions and service methods are extremely long.

The performance is bad and customization and maintenance is difficult. Fixing this should be top priority in my opinion.

Sorry to be so critical, I could also write many good things about nopCommerce.
3 years ago
fcastells wrote:
What about fixing the DB access and making all operations async? The nop team should look at this topic and take action.

Also, the architecture needs to be reviewed. It is not normal having controllers with 20 services injected in the constructor and in their turn, the services having 20 more services injected in their constructors. Also, many controller actions and service methods are extremely long.

The performance is bad and customization and maintenance is difficult. Fixing this should be top priority in my opinion.

Sorry to be so critical, I could also write many good things about nopCommerce.


I agree.  Right now we run our databases in Azure (Data Service) and run S2 with geo-replication.  Its $75 per month just for the database and after replication, its $150 per nop database. Web Server costs are all on top of that.  We tried lower plans on Azure, but the DTU just doesn't cut it for a site of any size.
From a "business value" perspective, the issues discussed in this topic are more important than jumping onto .net core.  If the goal of nopCommerce is to have dramatic growth in the community, then critical business needs like architecture optimization to alleviate high hosting costs need to be solved.  If the goal of nopCommerce is to push the latest in technology, then .net core migration makes sense.
There is a balance to be struck I believe... I think you should just have 2 work items for 4.0
1.  The planned .net core does have many attractive benefits, especially around handling web api, etc. and it could be leveraged for performance optimization.
2.  Architecture Optimization - Including async methods, etc.

Instead of a 8 month release window, release 4.0 when the above 2 items are ready.

All other features listed seem secondary and could wait until 4.1 (even price per currency work item).  If we optimize the plumbing, remove the barriers/high costs of handling larger sites more people will adopt the platform faster.

Please don't take the above statements the wrong way. I love nopCommerce and think the team has done a fantastic job.  I just want to see the product grow in the right direction.
Also: codeplex had a nice vote option...now that were in git, we need something similar to vote to help drive future road maps.

Thanks
3 years ago
Database Management in Nopcommerce
For example: https://github.com/OmniDB/OmniDB
3 years ago
Feature Folders - A feature folder structure is organizing your app by feature as opposed to technology (Controllers, Views, etc.)

There are many blogs/discussions about it out there - here's one example, and another.