Hey Philip

This is a known issue in Azure that for some reason it always reverts to System.Data.SqlClient when it should be using Microsoft.Data.SqlClient. Whilst it is Vendr's migrations that is throwing this error, Umbraco itself would suffer from the same issue as it's also built to use Microsoft.Data.SqlClient.

Generally speaking, you'd need to define a provider name entry in your connection strings section in app settings. You can find and example of it here https://vendr.net/docs/core/3.0.0/how-to-guides/use-an-alternative-database-for-vendr-tables/

Saying this though, some have still had problems with Azure reverting this and so they have had to setup those app settings in the azure portal. How you would do this on cloud though I have no idea.

It may be worth mentioning this to Cloud support as like I say, whilst it's a Vendr error, it's very much an Umbraco rooted issue too.

Hi Matt,

I've bumped the version in my project but the deploy is failing because it can't find the package on the default nuget feed.

I've opened a ticket with cloud to ask how to add a custom feed, but just leaving this here incase anyone else knows the answer.

Cheers

Phil

Good news, that's worked a treat 👍🏻 thanks so much for the quick turn around on that Matt I really appreciate it.

@Matt: Great to see you've already released a fix for this!

@Philip: Setting the provider name configuration values in appsettings.json won't work, because environment variables will overwrite them (at least in the default configuration source order).

Umbraco Cloud sets the environment variable SQLAZURECONNSTR_umbracoDbDSN to the Azure SQL Database connection string, which automatically sets ConnectionStrings:umbracoDbDSN to this connection string and ConnectionStrings:umbracoDbDSN_ProviderName to System.Data.SqlClient.

This works fine for Umbraco, because it will automatically change the provider name to Microsoft.Data.SqlClient on the ConnectionStrings options instance, ensuring the CMS/NPoco uses the correct provider to connect to the database.

Vendr 3 now uses its own database layer that also uses Microsoft.Data.SqlClient for SQL Server connection strings, hence it also needs to include a fix to automatically use the correct provider.

Hello,

I've got this exact issue at the moment and I can't seem to find a way to solve it. I've got the latest version of Vendr (3.0.3) and using Umbraco 10 on cloud.

Is there a way to solve this?

Thanks for any advice Becky

Hi Becky,

Add the unstable Vendr nuget feed to your Nuget package manager, here's the URL: https://nuget.outfield.digital/unstable/vendr/v3/index.json

Then install the latest pre-release version of Vendr Deploy, I am currently using 3.0.1-beta0001 and it works fine.

You'll also need to add the feed to the Nuget.config file at the absolute root of your cloud solution.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
    <add key="vendr.unstable" value="https://nuget.outfield.digital/unstable/vendr/v3/index.json" />
  </packageSources>

  <activePackageSource>
    <add key="All" value="(Aggregate source)" />
  </activePackageSource>

</configuration>

Hi Philip and Matt

Thank you so much for your quick reply.

Philip I have done that now. Matt, yes that was the exact message I was getting but I actually realised I had put the '.AddVendr' line in the wrong place so I have now moved that and I get pass that stage, however, I am now getting the following error, if either of you have any advice that would be really appreciated.

Edit to add - this is a current Umbraco 10 project we are trying to migrate to cloud, so vendr was installed before setting up the cloud project

This is a bit of a moonshot but have you tried completely deleting the folder in `/umbraco/deploy/revisions' and then re-running the deploy command from the Umbraco dashboard? From your local solution btw.

Also make if there are any attributes in your cloud environment it may be worth deleting them if you can get away with it.

Hi Matt and Philip

First, just want to apologise, I read this original post slightly wrong, the error I was getting was Sqlite not SqlClient.

I managed to solve this by uninstalling Vendr Deploy, running the project so that it would build and we could migrate stuff over from our old SqlServer database, and then reinstalled deploy and it all worked fine.

Thanks again for the help and advice from you both, and sorry to have accidentally jumped onto a thread about something slightly different!

is working on a reply...