Arra Derderian

My setup is Azure Functions V1 - .net framework 4.8 Middle layer is .net standard 2.0 with reference to Microsoft.Data.Sqlite Exception thrown while debugging in VS2019 is it can't load...

Thanks guys I will try now. I am using Azure Functions V1 right because I need to be running .net 4.8 for an old (eb) assembly to work. All seems...

 When I call it from Azure Functions V1 on app Startup. I added all those references.

Yes. I just switched it to force 64 bit and it now got past the : SQLitePCL.raw.SetProvider(new SQLitePCL.SQLite3Provider_e_sqlite3()); Same error though when I try and run a SqlCommand using Dapper...

Here is my .NET Standard data layer project :  And this is my Azure Function : 

Did that. Oddly now the WebApp that also uses this shared .NET Standard library will now not start with the error below. My Azure Function and the webapp share a...

So strange, so the WebApp has the following references. I use OrchardCore (which I love and have used for years). They use Sqlite as well. Could the bundle there be...

It's a tough predicament because at least in Functions V3, adding the e_sqlite3.dll to the bin solves it. And we only use SQlite for local dev anyways. But we need...

I can't really modify the core guts of OrchardCore and YesSQL, and my Azure functions layer shares a data layer with one of the custom modules I have built into...

I did not. I am not sure where I would insert that in the pipeline of the web app starting. I can't modify the underlying assembly references. It is getting...