Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/picrap/signreferences
Because open source causes CS1577 to strong naming fans.
https://github.com/picrap/signreferences
nuget references snk
Last synced: 14 days ago
JSON representation
Because open source causes CS1577 to strong naming fans.
- Host: GitHub
- URL: https://github.com/picrap/signreferences
- Owner: picrap
- License: mit
- Created: 2015-04-15T08:34:34.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2017-09-22T20:04:20.000Z (over 7 years ago)
- Last Synced: 2025-01-09T22:41:22.664Z (26 days ago)
- Topics: nuget, references, snk
- Language: C#
- Size: 541 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# SignReferences
*Because open source sometimes causes CS1577 to anger strong naming fans.*## How to use
Install the [NuGet package](https://www.nuget.org/packages/SignReferences/) on the project(s) where you need all references to be signed.
It can be installed from Visual Studio NuGet packager or from NuGet console using `Install-Package SignReferences`.## How it works
At build time, it simply checks for references, and signs in-place the ones who are unsigned.
This works very well with NuGet packages but also for assemblies referenced directly.Explicit `.snk` files can be specified, simply add a file named `SignReferences.txt` at the root of the project.
This file contains lines in the form of:
`: `
Wildcards are allowed, for example:
`Stuff.*: stuff.snk`
`Other.*: other.snk`
Assemblies not matching names provided in list will be signed with a default random-generated snk.
Snk file names are relative to project root.## Shall I be happy?
Yes. Probably.