Bouncy Castle for C# .NET FIPS, Strong Named Signing

[RyanPolk]

The Bouncy Castle .Net FIPS assembly 'bc-fips-1.0.2.dll' is not strong named, therefore we cannot directly reference it from our strong named projects. We're currently using Reflection to get around this, however it has been less than ideal.

Is there anyway that the Bouncy Castle .Net FIPS assembly can be strong name signed?
If not, are there any specific reasons for this?
Will 'bc-fips-2.0.0.dll' offer a strong name signed version?

Please let me know.

Thanks