ericsink / SQLitePCL.raw

A Portable Class Library (PCL) for low-level (raw) access to SQLite
Apache License 2.0
512 stars 106 forks source link

Assemblies in packages are not code signed, e.g. SQLitePCLRaw.provider.e_sqlite3.dll or SQLitePCLRaw.core.dll #581

Open AndreFo opened 5 months ago

AndreFo commented 5 months ago

We want to provide applications to our customer such that all required assemblies are code signed by their respective authors or companies or organizations. The package Microsoft.Data.Sqlite references SQLitePCLRaw packages which contain assemblies that are not code signed.

What version of SQLitePCLRaw are you using? 2.1.7

If you are using one of the SQLitePCLRaw bundle packages, which one?

We are using Microsoft.Data.Sqlite which references the following packages

What platform are you running on? What operating system? Which version? What CPU? netstandard2.0, Windows, Windows 10 or 11, x64 and x86

What target framework are you building for? NET6

Are you on .NET Framework or the newer stuff (.NET Core, .NET 5+, etc)? The newer stuff

Are you using the command line, or an IDE? Which IDE? Which version of that IDE? Visual Studio 2022

Is this problem something that just started happening? For example, were things working well for you and then you updated something and then the problem showed up? What changed? n/a

What is the exact error message you are seeing when the problem happens? n/a

Are you using PackageReference or packages.config? n/a

If you are using mobile platforms, are you on classic/legacy Xamarin or on .NET 6 and higher? .NET 6

Sometimes other packages using SQLitePCLRaw cause problems when they are mixed together. What other packages are you including in your project? no mixuture

How can we reproduce the problem you are seeing? Your issue will get attention much faster if you attach a minimal reproduction sample project. Nuget package explorer indicates signature for assemblies inside a nuget package.

marci4 commented 4 months ago

Hello everyone,

we are running into the same issue that the dlls are not code signed.

Is there a change to push this issue?

Best regards, Marcel