Dapper.Contrib.dll not signed

Open
#155 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
release

Research direction

The issue names no files, tests, or release entry points to inspect. Start by locating how Dapper.Contrib.dll is built and packaged, then determine the project's signing and release requirements; done means the released DLLs are signed and future releases preserve that property.

Written by the indexing model from the issue text.

Description

Would it be possible to do a release with the dlls signed (and maybe keep them signed going forward?)

We want to use your library, but our company can't release with unsigned dlls for security reasons

Thanks,

Matt

Dominant language
C#
Stars
293
Forks
109
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DapperLib/Dapper.Contrib

All issues in DapperLib/Dapper.Contrib

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.