New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strong naming in binaries #238
Comments
|
Original comment by |
Original comment by
|
Original comment by |
Original comment by |
Original comment by |
Original comment by |
|
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
|
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Original comment by |
Pre-release of zlib https://www.nuget.org/packages/Zlib.Portable.Signed/ |
In an attempt to keep everyone up to date, and get some feed back. With Peleyal's support I have been working on the following. Change(s).
Before we can strong name sign our library I needed to contact(trackdown) the owners of Zlib.Portable https://www.nuget.org/packages/Zlib.Portable/, and request that they sign it. As you know everything must be signed for this to work. This took a few weeks. I managed to track them down on twitter they have created a beta version for us to test with. https://www.nuget.org/packages/Zlib.Portable.Signed/1.11.0-beta1 What needs to be done before this can be merged:
Status:Over the weekend I added the zlib 1.11 - beta library to a fork of the Google .net client library, and signed all of the dlls. The branch can be found here https://github.com/LindaLawton/google-api-dotnet-client/tree/linda-Enhancement-238-StrongNameBinaries IssuesThe library appears to build and the dlls are created. I have tried to create a project using them, but have been running into some problems with miss matching dlls in Google.Apis.Auth.PlatformServices. I even tried using the email scope which doesn't require any of the discovery api dlls, so should have avoided any dependency issues. I have not been able to go more into it then that, due to time constraints. I suspect that I am mixing and matching different versions of the dll by mistake, I normally just grab the NuGet packages. It has been a long time since I have manually built the dlls and I am having a hard time remember how I did it last time. I will update this thread as I have more information for you. Again comments, concerns, and constrictive criticism are all welcome. Linda |
1. Fixed the string transformation where if a reserved keyword is used with invalid characters, we were not stripping out the invalid character when appending the reserved keyword with "__". This was causing something like '$object' to be transformed into '$object__' instead of 'object__' 2. Support Strong Named Assemblies in C# .NET Issue 238 (googleapis/google-api-dotnet-client#238) - Support Strong Named Assemblies Based on committing googleapis/google-api-dotnet-client#550 (was pushed on July 7th 2015) 3. Release 1.9.2 of the .NET client library for Google Apis. - Clone tempalte directory for 1.9.2 - Add 1.9.2 as test to targets.json - Clone golden tests for 1.9.2
Original issue reported on code.google.com by
atre...@gmail.com
on 12 Aug 2012 at 6:14The text was updated successfully, but these errors were encountered: