0

I need to reference the latest version of Bouncy Castle in a project I intend to publish to Github.

In my first posting of the code to Github, someone complained that I downloaded the entire Bouncy Castle library, added it as a project, and uploaded it.

What is the correct way to link to the latest version of this Bouncy Castle DLL so that my references are properly maintained?

2
  • Git Submodules are an option, although that adds significant complexity of its own.
    – amon
    Commented Feb 26, 2014 at 19:37
  • Are Bouncy Castle releases signed? If not download the repository, build it, the copy the output to your project. If you want a signed release you could in theory sign it yourself.
    – Ramhound
    Commented Feb 27, 2014 at 2:02

1 Answer 1

Reset to default
2

It looks like Bouncy Castle has a NuGet package. You could set up your VS2013 solution for package restore, and then reference Bouncy Castle through NuGet.

By doing so, you don't actually store the referenced files in your repository at all, just the NuGet reference. Then, when somebody else builds your project, the package restore process will download the files from the (NuGet) source for them.

2
  • That build is from Saturday, April 30 2011, I need the one from Feb 2014
    – makerofthings7
    Commented Feb 26, 2014 at 20:11
  • I see. I assumed you were looking for the latest released version, which is 1.7 from April 2011. You could always ask them to create a NuGet package for the latest beta version... NuGet is really the correct way to go to accomplish what you want.
    – Eric King
    Commented Feb 26, 2014 at 22:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.