I'll need to catch up with Bjarne to see where he was with the migration of this. I think he may have had it all there but was possibly waiting for my help to sort out the build script.
I've done this now so our deployment process is setup for this provider. It's currently compiled a v2.0.0-rc0001 on the Vendr Contrib unstable feed at https://nuget.outfield.digital/unstable/vendr-contrib/v3/index.json but I'll need to get confirmation from Bjarne that it is indeed ready to go before I create a final release.
Feel free to give the unstable build a try though 👍
Ok, unfortunately Bjarne does not work here anymore, or I could have given him a nudge myself 😁
But I gave it a try, but it wouldn't install
Unable to find a version of 'Lucene.Net.Contrib' that is compatible with 'Examine 2.0.0-beta2 constraint: Lucene.Net.Contrib (>= 3.0.3)'.
The Examine version on the project is 1.2.0
But I'm not sure this is a problem with this package, it might be the project I'm working on.
I needed to update Umbraco Deploy to fix a bug, the update was not available on Cloud, so Umbraco told me to do it manually.
Since then, I've been getting dependency errors, when installing or updating packages, where it either can't find packages that already are installed or it references newer versions than what's installed. Weird🤷♂️
But they are looking into it.
But I appreciate you taking the time to do this, and as soon as the other thing is fixed, I'll try again.
Vendr.Contrib.PaymentProviders.Nets not for Vendr v2?
Can the payment provider Vendr.Contrib.PaymentProviders.Nets not be used for v2?
If I look here https://github.com/vendrcontrib/vendr-payment-provider-nets there seems to be a v1 and v2 branch
But installing version 1.0.1 (the latest) via Nuget, gives me this error
And if I look at the dependences for the package https://www.nuget.org/packages/Vendr.Contrib.PaymentProviders.Nets/1.0.1 there is a dependency to Vendr.Core.Web (>= 1.4.0 && < 1.999999.0), which is v1.
Umbraco 8.17.0 Vendr 2.0.4
Hi Michael,
I'll need to catch up with Bjarne to see where he was with the migration of this. I think he may have had it all there but was possibly waiting for my help to sort out the build script.
I've done this now so our deployment process is setup for this provider. It's currently compiled a v2.0.0-rc0001 on the Vendr Contrib unstable feed at https://nuget.outfield.digital/unstable/vendr-contrib/v3/index.json but I'll need to get confirmation from Bjarne that it is indeed ready to go before I create a final release.
Feel free to give the unstable build a try though 👍
Matt
Ok, unfortunately Bjarne does not work here anymore, or I could have given him a nudge myself 😁
But I gave it a try, but it wouldn't install
The Examine version on the project is 1.2.0
But I'm not sure this is a problem with this package, it might be the project I'm working on.
I needed to update Umbraco Deploy to fix a bug, the update was not available on Cloud, so Umbraco told me to do it manually.
Since then, I've been getting dependency errors, when installing or updating packages, where it either can't find packages that already are installed or it references newer versions than what's installed. Weird🤷♂️
But they are looking into it.
But I appreciate you taking the time to do this, and as soon as the other thing is fixed, I'll try again.
I've seen this reported a few times now. For some reason Examine has a dependency on a beta package so you'll need to enable restoring prereleases.
Hopefully this will help a little bit. Solving dependency issues can be a nightmare 🤦♂️
Ok, how does one do that?
Can't seem to find anything related to it in any of the options in Visual Studio, or in the docs from Microsoft.
It's usually a checkbox in the NuGet package manager.
Looking at your error again though, I'm actually not sure if that is the same error so I may be leading you down the garden path there, sorry.
If this is a Vendr upgrade from v1 to v2, just as a tip, removing v1 and installing v2 seems to work best.
My dependency error was caused by Vendr.Deploy, uninstalling that solved the issue.
I'll investigate further if it's just a broken install, or anything that needs looked at further, and will report an issue if needed.
And yes, I know about the upgrade, it was me who did that, and wrote a post about it 😉
Lol, of course it was, it must still be my January brain struggling to get back into work after Christmas 😜
is working on a reply...