Hello all,
I want to upgrade NopCommerce from 4.50 to 4.60.
I use the .net source code, which I develop locally, then build and publish to my production webserver.
Following this guide:
https://docs.nopcommerce.com/en/installation-and-upgrading/upgrading-nopcommerce.html
... I see it states that once I've backed up appsettings.json and plugins.json, I should then delete anything else in App_Data, and then "Upload the new site files".
This is a little contentious to me; should I be downloading the latest source code files and just copy them over the top of the existing source code files? I assume this will result in quite a lot of overwriting, but also some old redundant files which are no longer used in 4.60.
Is this correct and OK? Or should I be taking a different approach?
Thanks!
Updating NopCommerce when using source code
MVP
认证开发者
- 3990
- 35617
- 2010/2/8
- Australia
michaeldrayson wrote:
This is a little contentious to me; should I be downloading the latest source code files and just copy them over the top of the existing source code files? I assume this will result in quite a lot of overwriting, but also some old redundant files which are no longer used in 4.60.
Is this correct and OK? Or should I be taking a different approach?
Thanks!
I would be starting with a new directory. Copy in the new v4.6 website files.
Minus the .json config files
Setup IIS and Directory Permissions
Then I run an Install to create a new test database and check everything works
Setup the App Settings and test
Then I will change the connection string to point to the old database
Install the plugins required (noting they need to be compatible with v4.6)
The good things is you can maintain you old system running while you upgrade
Ideally have a subdomain setup to test the new system as a staging site
When it is all ready to go swap the domains
This is a little contentious to me; should I be downloading the latest source code files and just copy them over the top of the existing source code files? I assume this will result in quite a lot of overwriting, but also some old redundant files which are no longer used in 4.60.
Is this correct and OK? Or should I be taking a different approach?
Thanks!
I would be starting with a new directory. Copy in the new v4.6 website files.
Minus the .json config files
Setup IIS and Directory Permissions
Then I run an Install to create a new test database and check everything works
Setup the App Settings and test
Then I will change the connection string to point to the old database
Install the plugins required (noting they need to be compatible with v4.6)
The good things is you can maintain you old system running while you upgrade
Ideally have a subdomain setup to test the new system as a staging site
When it is all ready to go swap the domains
MVP
认证开发者
- 3990
- 35617
- 2010/2/8
- Australia
Checking this post seems they had problems with Visual Studio Code
See https://www.nopcommerce.com/en/boards/topic/97152/missing-plugins-when-building-with-visual-studio-code
Others recommended they use Visual Studio
See https://www.nopcommerce.com/en/boards/topic/97152/missing-plugins-when-building-with-visual-studio-code
Others recommended they use Visual Studio
- 1
- 5
- 2022/12/2
- Brazil
Yidna wrote:
This is a little contentious to me; should I be downloading the latest source code files and just copy them over the top of the existing source code files? I assume this will result in quite a lot of overwriting, but also some old redundant files which are no longer used in 4.60.
Is this correct and OK? Or should I be taking a different approach?
Thanks!
I would be starting with a new directory. Copy in the new v4.6 website files.
Minus the .json config files
Setup IIS and Directory Permissions
Then I run an Install to create a new test database and check everything works
Setup the App Settings and test
Then I will change the connection string to point to the old database
Install the plugins required (noting they need to be compatible with v4.6)
The good things is you can maintain you old system running while you upgrade
Ideally have a subdomain setup to test the new system as a staging site
When it is all ready to go swap the domains
I'm facing the same scenario, and my Nop version is 4.20. I saw in the documentation that it needs to be version over version. It's OK!
But I have custom plugins that will probably have to be adapted for 4.30 and beyond. I just want to check if this is the way.
Thanks!
This is a little contentious to me; should I be downloading the latest source code files and just copy them over the top of the existing source code files? I assume this will result in quite a lot of overwriting, but also some old redundant files which are no longer used in 4.60.
Is this correct and OK? Or should I be taking a different approach?
Thanks!
I would be starting with a new directory. Copy in the new v4.6 website files.
Minus the .json config files
Setup IIS and Directory Permissions
Then I run an Install to create a new test database and check everything works
Setup the App Settings and test
Then I will change the connection string to point to the old database
Install the plugins required (noting they need to be compatible with v4.6)
The good things is you can maintain you old system running while you upgrade
Ideally have a subdomain setup to test the new system as a staging site
When it is all ready to go swap the domains
I'm facing the same scenario, and my Nop version is 4.20. I saw in the documentation that it needs to be version over version. It's OK!
But I have custom plugins that will probably have to be adapted for 4.30 and beyond. I just want to check if this is the way.
Thanks!
MVP
认证开发者
- 3990
- 35617
- 2010/2/8
- Australia
Not sure what you are asking ?
The plugins would just need to be changed to work with the final version i.e. v4.6
Also depening on what the plugin does, sometimes it maybe easier to take a current v4.6 plugin and use it as a base to build a new plugin adding in the the old modifications from v4.3 rather than upgrade the v4.3 plugin.
The plugins would just need to be changed to work with the final version i.e. v4.6
Also depening on what the plugin does, sometimes it maybe easier to take a current v4.6 plugin and use it as a base to build a new plugin adding in the the old modifications from v4.3 rather than upgrade the v4.3 plugin.