Florian Hockmann commented on TINKERPOP-1880:

Ok, so if I understand it correctly now, then we have basically three options 
to deploy Nuget packages until we resolved the strong-name signing problem:
 # [~pluradj] _volunteers_ to do it.
 # The PMC decides to give a committer with the necessary environment the 
authorization for NuGet deployments.
 # I use the fact that I still am registered as an owner of the package and do 
the deployment. (Should probably also be decided by the PMC, so basically the 
same as option 2. Since we decided to remove me as an owner, this would really 
only be a very temporary solution.)

> Gremlin.NET Strong name signature could not be verified. (HRESULT: 0x80131045)
> ------------------------------------------------------------------------------
>                 Key: TINKERPOP-1880
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1880
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: dotnet
>    Affects Versions: 3.2.7, 3.3.1
>         Environment: Windows 10, IIS Express 10, .Net Framework 4.7.1
>            Reporter: Klaus Stephan
>            Priority: Major
>         Attachments: 31-01-_2018_14-50-15.png
> I am trying to use the Gremlin.NET nuget package in a web application (.NET 
> Framework 4.7.1).
> The project builds successfully, but when starting it in IIS Express, I get 
> an error
> "Strong name signature could not be verified. (HRESULT: 0x80131045)"
> I tried different versions, but always get the same error.
> Please fix the nuget packages so that they become usable.

This message was sent by Atlassian JIRA

Reply via email to