This project has moved and is read-only. For the latest updates, please go here.

Assembly with strong name



Could you please release NAudio as an assembly with a strong name so it can be installed in the GAC by running gacutil -i NAudio.dll?



markheath wrote Jan 22, 2010 at 3:04 PM

it's not a bad idea. I'll bear it in mind for the next NAudio release

ChrisBradfield wrote Jul 27, 2011 at 12:40 PM

We'd like to release our application signed using strong names, but can't do this if NAudio isn't also strongly name.

JustinPihony wrote Feb 25, 2013 at 5:52 PM


markheath wrote Feb 25, 2013 at 7:11 PM

I'm afraid I don't currently have any plans to do this. It seems to cause more problems than it solves (and I don't really want to start publishing two editions of NAudio). My recommendations if your company really really needs signed DLLs for some reason:
1) sign it yourselves
2) hire me to make a special signed version just for you ;)

MikNik wrote Feb 9, 2015 at 9:41 PM

There shouldn't be any problems, just open the project file in Visual Studio, in Properties find a Signing tab and create a new pair of keys, which should then be added to all projects - or to a common AssemblyInfo, if you have such one :-)

Jokes aside, it'd be really nice to have a signed version in order to avoid fetching the source code for recompilation/resigning... Nuget does the job of getting the library, I'd rather not intervene with it :-)

markheath wrote Feb 12, 2015 at 9:06 PM

This is a long-running debate in the .NET development community. Unfortunately signing assemblies can cause as many problems as it solves.