nopCommerce 3.00 roadmap. Let's discuss.

leandromugnol wrote:

you should move to iis 7.0++ or even 8.0 + .net 4.5 which can boost the performance better (entity framework 5.0 is faster than 4.x). The problem is if your iis recycling is too small, then your sites might be slow because it could break Nop caching system and asp.net doesn't work well like scripting languages like php or classic asp in the first boot.

I'm running dozens of nop sites 2.7 with my own custom code, so far so good. Can't wait for 3.0 multi stores !!

SignalR (http://signalr.net/)  officially released by MS MVC team (http://weblogs.asp.net/scottgu/archive/2013/02/18/announcing-release-of-asp-net-and-web-tools-2012-2-update.aspx)

http://www.strathweb.com/2013/02/signalr-actionfilters-and-asp-net-web-api/

In case you guys need to improve real-time functionality, take a look at that.

congthanhgiong wrote:
For example? There's no any real-time functionality used in nopCommerce

Hey

Can we do any work-around to create multi-stores till we get 3.0 release, because we cannot stop the project implementation till that time.
please provide us about any idea in the current release to create multi-stores.

asaid.moussa wrote:
https://www.nopcommerce.com/boards/t/21356/multi-store-roadmap-lets-discuss-update-done.aspx

Hi Andrei,

Great news to hear that multistore support is already done!

I was hoping you could give me some more information on multi vendor support as well? I happen to need multi vendor support in my current project and was planning do the customization myself. Maybe we could join forces?

Or at least can you share with me the planned changes to the database model that will enable multi vendor support?

Looking forward to hear from you.

rudgr wrote:
I haven't thought about multi-vendor support and how it'll be implemented yet

a.m. wrote:
quick question, if we apply the changeset 80e3252fc205 and then upgrade after 3.0 come out will it have any effect on the configurations as based on my previous knowledge it is not recommended to apply unstable changesets to production

SDSharp wrote:
a.m. wrote:

Hi a.m.,

Thanks for bringing the topic of nopC 3.0 and its roadmap up, and thanks for the great work that was done so far in nopCommerce. I remember I have evaluated nopCommerce two years ago, and it wasn't my first choice at that time. Today, I would confidently say that in the last two years, nopCommerce has achieved one of the highest market share increase rates among all shopping cart providers.

Back to the 3.0 roadmap topic, IMHO, a simpler and more generic approach for the Wine Club suggestion is to add a "Make this order recurrent" button next to each order in the Orders page of the customer. A customer may click on this button and select the recurrence pattern (e.g. weekly, monthly, quarterly, ...etc.). A new tab that shows "Recurrent Orders" under "My Account" may be developed. When a recurrent order is automatically generated by the system on behalf of the customer, this very instance of the order is forked and saved as a regular order.

I think most of the functionalities needed to support this feature are already implemented, such as the system's current ability to (1) make recurrent payments, (2) mark product variants as recurring products and specify a recurring cycle, and (3) allow the customer to re-order a previous order.

infiniti wrote:
Sure, you can use it. But only on your own risk