[jira] [Commented] (TINKERPOP-1880) Gremlin.NET Strong name signature could not be verified. (HRESULT: 0x80131045)
[
https://issues.apache.org/jira/browse/TINKERPOP-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358446#comment-16358446
]
Jorge Bay commented on TINKERPOP-1880:
--
I've just downloaded the latest dotnet sdk on macOS and try to sign an assembly
and the error is clear:
{code}
Error signing output with public key from file '../key.snk' -- Assembly signing
not supported
{code}
So I think using an external service like appveyor is the easiest route for
upcoming releases.
> 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
(v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1880) Gremlin.NET Strong name signature could not be verified. (HRESULT: 0x80131045)
[ https://issues.apache.org/jira/browse/TINKERPOP-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358390#comment-16358390 ] Jorge Bay commented on TINKERPOP-1880: -- The release manager can then download the package from AppVeyor and push it to nuget.org. > 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 (v7.6.3#76005)
[jira] [Commented] (TINKERPOP-1880) Gremlin.NET Strong name signature could not be verified. (HRESULT: 0x80131045)
[ https://issues.apache.org/jira/browse/TINKERPOP-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358381#comment-16358381 ] Jorge Bay commented on TINKERPOP-1880: -- If there isn't a way of building a signed .NET assembly from macOS / linux with the current dotnet toolchain, we could use AppVeyor. AppVeyor is, like TravisCI, free for OSS projects, provides Windows VMs and the possibility to package artifacts: https://www.appveyor.com/docs/packaging-artifacts/ > 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 (v7.6.3#76005)
