Skip to content

ellenfieldn/Flurl.Signed

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

70 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Flurl.Signed

Sometimes life isn't fair and you are stuck supporting the world as it existed 10+ years ago. So if you'd like to use the amazing Flurl, but for whatever reason are still using strong naming, I've signed and repackaged them for you.

Enjoy!

NuGet Packages:

Caveats

  • These are not built from source, they simply sign the existing assemblies on NuGet and publish them back to NuGet.

Acknowledgements

Roadmap

I don't think I plan to do too much to this given that it already works, but some things that would be fun and make it more robust that I may be able to find time for:

  • Separate the nuget package generation from the uploading to the nuget repository.
  • Add verification of the nuget packages with sn.exe
  • Add integration tests to verify consumption of the nuget packages
  • Push based on results of verification and integration tests

How it works

For anyone who wants to replicate this, here's how:

Generating a signing key

  1. Open Visual Studio Powershell as Administrator
  2. Run sn -k Flurl.Signed.snk
  3. Encode as base64 by running the command certutil -encodehex -f .\Flurl.Signed.snk Flurl.Signed.encoded.txt 0x40000001
  4. Add as Secret "NUGET_SIGNING_KEY" to github repo

About

These are the original Flurl NuGet packages repackaged with signed assemblies

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Sponsor this project

 

Packages

No packages published

Languages

  • PowerShell 100.0%