Feature Request
Provide NuGet Packages for RayGun4Net as Signed Assembly
Current Status:
Completed
MarkLFT
I am using RayGun4Net in several apps, and would like to use the NuGet functionality, but am unable to do so as the assembly installed is unsigned.
This means I must get the source code, and sign it myself, then, use it. Or, I must use the .Net IL tools to sign it. Either way I am losing out on the advantage of ease of installation, and easy access to updates. Obviously features you felt were important enough to add the library to NuGet in the first place.
Can you not, like most other 3rd party library suppliers, sign the assembly before adding it to NuGet?
Raygun
jeremy
Posted on
Oct 07 2013
At this stage we are providing a non signed version to help avoid versioning issues. Our own experience with commonly linked assemblies that are strong named has been tainted by issues (e.g. JSON.NET) leading to binding redirect pains so we chose not to sign the assembly as part of our build process for that reason. We do also have the source available (as you noted) to provide this option where required.
That said we are certainly open to some discussion on this, so it would help to understand a bit more about why signing would be useful so we can consider this further. Is it just that you are signing your assemblies so need to link to a strong named version?
Jeremy
MarkLFT
Posted on
Oct 07 2013
The reason behind my request is pretty simple,I prefer to use the NuGet option for all libraries such as your own, plus log4net, and several other libraries. This makes it easy to use them, ensures I get the correct dependencies, and am notified of any updates. I am sure you will agree, all good things.
However, because your library does not have a strong name, when I try to build my app, which must have a strong name, with the NuGet version, the build fails.
As a workaround I have downloaded your code, and built a strong name version, which allows me to use Raygun in my app. However, I recently, by chance found you had an updated version of this library, so I had to download a new version and build another strong name version. Not a big job, but an annoying waste of time, when we now have technologies like NuGet to prevent this type of task.
Pretty much every library I use these days has a strong name version, so I do not think it is an unreasonable request that you guys provide the same.
Thanks for your understanding.
Raygun
John-Daniel Trask
Posted on
Jul 24 2014
This can now be found here: https://www.nuget.org/packages/Mindscape.Raygun4Net.Signed/
I hope that helps!
John-Daniel Trask
G P Zob
Posted on
Mar 30 2016
Mindscape.Raygun4Net.Signed is great.
But what about having:
Mindscape.Raygun4Net.WebApi.Signed
and
Mindscape.Raygun4Net.Mvc.Signed
It makes sense to supply these also.