[
https://issues.apache.org/jira/browse/IGNITE-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062116#comment-15062116
]
Igor Sapego commented on IGNITE-2186:
-------------------------------------
For the Visual Studio there are several different versions that should be
changed from different places:
1. [Assembly
Version|https://msdn.microsoft.com/en-us/library/aa374234(v=vs.85).aspx], which
is set in manifest file of the project. Our C++ projects does not have
manifests currently.
2. [Version linker
option|https://msdn.microsoft.com/en-us/library/h88b7dc8.aspx], which is set in
project settings. This version is put directly in the header of the .dll file.
3. [VERSIONINFO resource
file|https://msdn.microsoft.com/en-us/library/windows/desktop/aa381058(v=vs.85).aspx]
for project. This version is displayed in file properties in "Details" tab.
> CPP: Investigate version policies for Visual Studio.
> ----------------------------------------------------
>
> Key: IGNITE-2186
> URL: https://issues.apache.org/jira/browse/IGNITE-2186
> Project: Ignite
> Issue Type: Task
> Components: interop
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Igor Sapego
> Priority: Critical
> Fix For: 1.5
>
>
> Starting from this release we gave different version scheme - suffix is
> added. E.g.: 1.5.0-b1, 1.5.0-GA, etc.
> We need to understand how to properly handle this case with Visual Studio so
> that correct version is reflected in DLL metadata. Can we simply set this
> string as version?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
