[
https://issues.apache.org/jira/browse/TINKERPOP-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172953#comment-16172953
]
ASF GitHub Bot commented on TINKERPOP-1785:
-------------------------------------------
Github user jorgebay commented on the issue:
https://github.com/apache/tinkerpop/pull/716
We forgot to consider that, as we are strong named assembly, we must avoid
changing the assembly version for patch versions to minimize the need of
user-defined binding redirects.
In our case, it would mean to set a fix assembly version within the same
major and minor. The generated Gremlin.Net.csproj should contain the 3
following xml tags:
```xml
<!-- Version: 3.2.7 -->
<Version>$projectVersion</Version>
<!-- FileVersion: 3.2.7.0 -->
<FileVersion>$projectVersion.0</FileVersion>
<!-- AssemblyVersion: 3.2.0.0 -->
<AssemblyVersion>$projectMajorMinorVersion.0.0</AssemblyVersion>
```
> Gremlin.Net should be strong-name signed
> ----------------------------------------
>
> Key: TINKERPOP-1785
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1785
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.3.0, 3.2.6
> Reporter: Florian Hockmann
> Priority: Minor
>
> Users that strong-name sign their assemblies currently cannot use our
> Gremlin.Net NuGet packages as they are not strong-name signed as strong-named
> assemblies can only reference strong-named assemblies.
> I [just strong-name signed the pre-GLV
> version|https://github.com/FlorianHockmann/Gremlin.Net/pull/13] of
> Gremlin.Net as it [was requested by
> users|https://github.com/FlorianHockmann/Gremlin.Net/issues/12].
> More information about strong-naming:
> https://docs.microsoft.com/en-us/dotnet/framework/app-domains/strong-named-assemblies
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
