[ https://issues.apache.org/jira/browse/TINKERPOP-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347007#comment-16347007 ]
Jorge Bay commented on TINKERPOP-1880: -------------------------------------- I think the underlying issue is related to making the release from a non-windows environment: https://github.com/apache/tinkerpop/blob/3.3.1/gremlin-dotnet/src/Gremlin.Net/Gremlin.Net.csproj#L54 Background: - https://github.com/dotnet/roslyn/issues/8210 - https://github.com/dotnet/cli/issues/6911 I don't know if with newer versions of the dotnet build toolchain we are be able to release from non-windows envs ...? Oh man, I hate strongly signed assemblies. > 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)