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

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
6 years ago
I would love the ability to show product Availability on the one-page checkout.

Right now, my customers have no idea about factory lead time unless they open up each product page individually.
6 years ago
Please let me add that we don't recommend to use development branch in production. Please wait until 4.00 is released or use 3.90
6 years ago
ChuckR 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


I agree.
@Team: any plans for reviewing & improving the architecture?
6 years ago
Hi NopCommerce Team,

Is nop team planning on updating the target to any other version or it will start in .net 4.6.1 in 4.0 production?

I have downloaded latest beta version from github when I tried to create a core plugin that targeting to asp.net core 1.1 then I get errors related to nuget.
so my question is -  

How the project is targeting .net 4.6.1 when project is in core?


If I want to create a test Plugin in 4.0. I should use target .net 4.6.1? how can I write code in core with Target 4.6.1? I thought core requires core 1.1 target?
6 years ago
harshitporwal wrote:
Hi NopCommerce Team,

Is nop team planning on updating the target to any other version or it will start in .net 4.6.1 in 4.0 production?

I have downloaded latest beta version from github when I tried to create a core plugin that targeting to asp.net core 1.1 then I get errors related to nuget.
so my question is -  

How the project is targeting .net 4.6.1 when project is in core?


If I want to create a test Plugin in 4.0. I should use target .net 4.6.1? how can I write code in core with Target 4.6.1? I thought core requires core 1.1 target?


looks like this is not real .net core to me, as it still reuse legacy libs from the old .net. Also the Entity framework is still 6.x, isn't it? Would we stay with this 1.1 or move to 2.0 in this version ?
6 years ago
namvo wrote:
Hi NopCommerce Team,

Is nop team planning on updating the target to any other version or it will start in .net 4.6.1 in 4.0 production?

I have downloaded latest beta version from github when I tried to create a core plugin that targeting to asp.net core 1.1 then I get errors related to nuget.
so my question is -  

How the project is targeting .net 4.6.1 when project is in core?


If I want to create a test Plugin in 4.0. I should use target .net 4.6.1? how can I write code in core with Target 4.6.1? I thought core requires core 1.1 target?

looks like this is not real .net core to me, as it still reuse legacy libs from the old .net. Also the Entity framework is still 6.x, isn't it? Would we stay with this 1.1 or move to 2.0 in this version ?


Will it be 1.1?!
6 years ago
Right now we use ASP.NET Core 2 (based on .NET Framework 4.6.1). We don't use .NET Core now just because EF Core doesn't support lazy loading, etc. So we wait for EF Core team to implement it. Here is a work item
6 years ago
Any update on specific release date? Very excited!
6 years ago
niscoteam wrote:
Any update on specific release date? Very excited!

We plan to release BETA in the beginning of October. And the final version in aboub 3 weeks after BETA
6 years ago
nop team

I'm testing the 4.0  BETA from github and it is not working.

(Nop.Web is startup)

ERROR
Unable to start process
The system cannot find the file specified
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.