DapperLib / DapperLib/Dapper.Contrib
Dapper.Contrib.dll not signed
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 293
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- csharp
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100