No strong naming in NuGet?

May 16, 2013 at 11:37 PM
I am using the latest version of the System.Net.FtpClient package from NuGet, however the library is not strong named. It is possible to have this re-build and published with a strong name key file in it?
Coordinator
May 17, 2013 at 2:57 PM
I've modified the package build script to tell msbuild to sign the release assembly using a newly created SN key pair generated for this project:
>sn -v System.Net.FtpClient.dll

Microsoft (R) .NET Framework Strong Name Utility  Version 4.0.30319.17929
Copyright (c) Microsoft Corporation.  All rights reserved.

Assembly 'System.Net.FtpClient.dll' is valid
The most current nuget package should include this dll.
May 17, 2013 at 4:45 PM
Thanks, I will give it a try!
May 17, 2013 at 5:54 PM
What happened to the FtpClient.Download() functions that used to exist in the earlier versions?
Coordinator
May 17, 2013 at 6:00 PM
They haven't existed for quite a while. That code is under the System.Net.FtpClient_1 branch under the source tab. There are no binaries of that code base available and the only changes it receives are the occasional maintenance updates by StrAbZ.
May 17, 2013 at 6:21 PM
Ok. I will just write my own utility class based on the old code and use the new library.