I just had a bit of an issue with the Csla-Core NuGet package. Basically because the dependency specifies Bcl.Async >= 1.0.165 if you install Csla today it will grab the latest, which also depends on a later Bcl version as well. The issue is that Csla itself is built against System.Runtime 2.6.6, which caused an issue with FxCop as NuGet got 2.6.7 and FxCop will not let you use 2.6.7 in place of 2.6.6. I'm not sure if this is because Csla is strong named too.
Also, is there any reason to strong name Csla? If there is can we have a -Unsigned package as well?