Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
AndreFo opened this issue Jan 11, 2024 · 1 comment

Comments

@AndreFo
Copy link

AndreFo commented Jan 11, 2024

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

  • SQLitePCLRaw.core
  • SQLitePCLRaw.lib.e_sqlite3
  • SQLitePCLRaw.provider.e_sqlite3

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
Copy link

marci4 commented Feb 14, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants