I have extended Affiliate Module in NopCommerce 2.6 by adding two new fields like "WebsiteURL" and "Picture Upload". For that I have made changes in Affiliate Services, Affiliate Controller, Affiliate.cs,Affiliate Map,Affiliate Model files. Now If I want to make update this feature in next version of NopCommerce then how can I Integrate this functionality in that. Is there any way to do this automatically? or I have to do this customization manually?
I would like to learn how to customize in a way that helps in customization for future upgradation of NopCommerce.
How to preserve customization while upgrading to a new version?
- 329
- 4194
- 4/27/2010
- Netherlands
Your options are:
1. Create a plugin. This will preserve while upgrading
2. Create an alternative implementation by implementing the appropriate interfaces and changing the DI. This may or may not preserve depending on the changes but it is more isolated than option 3.
3. Make changes to the nop files directly. This will NOT preserve while upgrading
1. Create a plugin. This will preserve while upgrading
2. Create an alternative implementation by implementing the appropriate interfaces and changing the DI. This may or may not preserve depending on the changes but it is more isolated than option 3.
3. Make changes to the nop files directly. This will NOT preserve while upgrading
- 377
- 3241
- 9/12/2011
- India
keesjan wrote:
Can you elaborate this point in detail please? It's better if you give an example with it.
Your options are:
2. Create an alternative implementation by implementing the appropriate interfaces and changing the DI. This may or may not preserve depending on the changes but it is more isolated than option 3.
2. Create an alternative implementation by implementing the appropriate interfaces and changing the DI. This may or may not preserve depending on the changes but it is more isolated than option 3.
Can you elaborate this point in detail please? It's better if you give an example with it.
- 329
- 4194
- 4/27/2010
- Netherlands
Dharmik wrote:
Instead of making changes to AffiliateService, creat a new class MyAffiliateService and implement IAffiliateService, forward the methods you don't want to change to AffiliateService and change the methods you want. This will isolate your changes and makes it easier to upgrade
Your options are:
2. Create an alternative implementation by implementing the appropriate interfaces and changing the DI. This may or may not preserve depending on the changes but it is more isolated than option 3.
Can you elaborate this point in detail please? It's better if you give an example with it.
2. Create an alternative implementation by implementing the appropriate interfaces and changing the DI. This may or may not preserve depending on the changes but it is more isolated than option 3.
Can you elaborate this point in detail please? It's better if you give an example with it.
Instead of making changes to AffiliateService, creat a new class MyAffiliateService and implement IAffiliateService, forward the methods you don't want to change to AffiliateService and change the methods you want. This will isolate your changes and makes it easier to upgrade
- 329
- 4194
- 4/27/2010
- Netherlands
jariwalakrunal wrote:
Was speaking in general, not everything can be done with plugins but it would be very nice if it could
Vote for this workitem to get NC in that direction
http://nopcommerce.codeplex.com/workitem/11006
Can you please explain how to make such changes using Plugin? Any hel for this specific requirement will be great for community to understand.
Was speaking in general, not everything can be done with plugins but it would be very nice if it could
Vote for this workitem to get NC in that direction
http://nopcommerce.codeplex.com/workitem/11006
- 377
- 3241
- 9/12/2011
- India
keesjan wrote:
If I make one new class library for these types of customizations , then what will be challenges ? Is this right way to do this?
Because if this may happen then it would be great to upgrade to new version.
What do you think guys?
Your options are:
2. Create an alternative implementation by implementing the appropriate interfaces and changing the DI. This may or may not preserve depending on the changes but it is more isolated than option 3.
Can you elaborate this point in detail please? It's better if you give an example with it.
Instead of making changes to AffiliateService, creat a new class MyAffiliateService and implement IAffiliateService, forward the methods you don't want to change to AffiliateService and change the methods you want. This will isolate your changes and makes it easier to upgrade
2. Create an alternative implementation by implementing the appropriate interfaces and changing the DI. This may or may not preserve depending on the changes but it is more isolated than option 3.
Can you elaborate this point in detail please? It's better if you give an example with it.
Instead of making changes to AffiliateService, creat a new class MyAffiliateService and implement IAffiliateService, forward the methods you don't want to change to AffiliateService and change the methods you want. This will isolate your changes and makes it easier to upgrade
If I make one new class library for these types of customizations , then what will be challenges ? Is this right way to do this?
Because if this may happen then it would be great to upgrade to new version.
What do you think guys?