I haven't seen anything in the documentation on how to do this. But I thought I would give it at try.
As the project structure of Vendr changes between the versions, just updating the nuget packages is not possible.
So what I did was the following:
Stop my local IIS site
Uninstall all Vendr packages
Install Vendr 2.x
Update code where needed. For me it was adding, removing or replacing some usings, as a few things has moved to a different project and namespace. Also a couple of things either now requires or no longer requires a parameter, so changed these as well. All in all it took about 10 minutes to go through.
Started the site again and visited the frontend
After startup, I tested that everything still works, which it does. So I don't know if that would be the correct way to do it, but it worked. 🤷♂️
This is indeed the exact same process I went through for the demo store as I found the same, because the nuget packages have changed around a bit, it doesn't seem to like a straight upgrade so removing and re-installing seemed to be the way to go.
The only extra thing I'd probably add is that the invoice payment provider is now part of core, so if you have a reference to that as a nuget package, it can be completely removed now.
I'll see what I can do about getting some docs written though, but in the meantime this is a very good outline of the process 👍
And then upgraded to v2, where the property is removed from the store. It will still use the set value, and not the file using the naming convention {storeAlias}.order.editor.config.js
It can be easily fixed by removing or renaming the file used n the v1 setting, it will then start using the file using the naming convention {storeAlias}.order.editor.config.js
Yea, I didn't know what was best there so I just made it use whatever value was configured, but yea, maybe I need to make the file based one's take precedence and only try old DB field as a fallback 👍
Upgrade from 1.x to 2.x
I haven't seen anything in the documentation on how to do this. But I thought I would give it at try.
As the project structure of Vendr changes between the versions, just updating the nuget packages is not possible.
So what I did was the following:
After startup, I tested that everything still works, which it does. So I don't know if that would be the correct way to do it, but it worked. 🤷♂️
Hey Michael,
Thank you for sharing this for everyone else 🙏
This is indeed the exact same process I went through for the demo store as I found the same, because the nuget packages have changed around a bit, it doesn't seem to like a straight upgrade so removing and re-installing seemed to be the way to go.
The only extra thing I'd probably add is that the invoice payment provider is now part of core, so if you have a reference to that as a nuget package, it can be completely removed now.
I'll see what I can do about getting some docs written though, but in the meantime this is a very good outline of the process 👍
Matt
Hi Matt
Good to hear!
And yes I unstalled Invoice Payment Provider along with the rest of the Vendr packages.
One curious thing I found, not sure I'd call it a bug, but maybe you want to 'fix' it 🤷♂️
If you in v1 assigned an order editor config, in a property on the store
https://vendr.net/docs/core/1.8.0/key-concepts/order-editor-config/#assigning-an-order-editor-config-file-to-a-store
And then upgraded to v2, where the property is removed from the store. It will still use the set value, and not the file using the naming convention
{storeAlias}.order.editor.config.jshttps://vendr.net/docs/core/2.0.0/umbraco-v9/key-concepts/order-editor-config/#assigning-an-order-editor-config-file-to-a-store
It can be easily fixed by removing or renaming the file used n the v1 setting, it will then start using the file using the naming convention
{storeAlias}.order.editor.config.jsYea, I didn't know what was best there so I just made it use whatever value was configured, but yea, maybe I need to make the file based one's take precedence and only try old DB field as a fallback 👍
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.