Making NopCommerce easy to upgrade when doing custom code changes.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
5 years ago
Hi.
We have a NopCommerce website that is written for version 3.9. We are thinking about upgrading to the newest version (4.1). The problem is that we have a lot of custom code in all kinds of places. For example: Nop.Core.Domain.Catalog.CatalogSettings has a few added properties and Nop.Core.Domain.Catalog.ProductAttributeCombination has a few added properties as well as a method and a getter setter method.

Is there any common way to separate the added code from the core code so that upgrading to a future release is as easy as copying a few folders over to the new store?
How are people handling this?
Is there some common best practice to handle this?

Thanks
5 years ago
Hello,

Best practices are to convert your code to external plugin.

So in feature you have to just upgrade your plugin.

Otherwise, you have to write specific comment on your method so it is very easy to find.

If you have external module which is not possible through plugin than you have to bring in separate folder like CustomCode(foldername)  in which you have to put your controller, model and view page etc.

Keep those things in your mind and start your up gradation process.

Hope you will understand.
5 years ago
So all of the custom code that you add to your nopCommerce store should be in plugins?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.