Efcore: The process has no package identity

[TonyValenti]

Using EFCore with SQLITE now causes the error:
System.InvalidOperationException: 'The process has no package identity. (Exception from HRESULT: 0x80073D54)'

From the following module:
Microsoft.Data.Sqlite.Utilities.ApplicationDataHelper.LoadAppData

It looks like it is using reflection to do some calls. Can this be updated to not throw?

[ajcvickers]

@TonyValenti Please attach a small, runnable project or post a small, runnable code listing that reproduces what you are seeing so that we can investigate.

[NatPerat]

I have the same problem. Just updated Microsoft.EntityFrameworkCore.Sqlite to 3.1.5
Here's a little reproduction
ConsoleApp1.zip

[ajcvickers]

@TonyValenti @NatPerat I ran the project on two machines (Ubuntu Linux and Windows 10) and it worked fine in both places. Which operating system/version are you on where this is failing?

[TonyValenti]

@ajcvickers - The exception is an internal one that is swallowed by the code. In VS, tell it to break on every exception and you'll see it happen.

[ajcvickers]

@TonyValenti I still don't see an exception. However, a handled exception in this case is by-design. Why is this causing issues for you?

[NatPerat]

The project seems to be running fine regardless of the exception. But I was worried it might have other implications. The System.InvalidOperationException was not there in the previous versions. So when I searched and found this issue I thought I should dig a little.

I run windows 10 with the latest dotnet core sdk and the .net framework 4.8 alongside.

Long time user, love the project. Thanks for your time.

[jeroenwalter]

I have this exact same issue, even disabling all C# exceptions in the exception settings won't help. The program consistently breaks when trying to open a sqlite connection.
The console app provided earlier as an example also reproduces this problem for me.
I'm running vs2019 16.6.2.
So as a consequence, each time I run my program in the debugger, I get this exception thrown in my face, then have to press F5 to continue debugging.

[knilecrack]

I have same issue as @jeroenwalter, it runs fine .net core, but for .net 4.8, same exception.
edit: Not related to EF Core, have same issue with Dapper.

[jeroenwalter]

I got rid of this exception after enabling the "Enable Just my code" option in the debugging options....