Skip to content

Bump ApplicationVersion to 1.3.0.0#7

Merged
mattock merged 2 commits intoOpenVPN:masterfrom
mattock:master
Dec 29, 2016
Merged

Bump ApplicationVersion to 1.3.0.0#7
mattock merged 2 commits intoOpenVPN:masterfrom
mattock:master

Conversation

@mattock
Copy link
Copy Markdown
Member

@mattock mattock commented Nov 25, 2016

No description provided.

Signed-off-by: Samuli Seppänen <samuli@openvpn.net>
@mattock
Copy link
Copy Markdown
Member Author

mattock commented Nov 25, 2016

Version 1.3.0.0 is released with openvpn 2.4_beta2. Is there some other place for the version number which would show up in "File properties" dialog in Windows? I don't think this has any effect there, but I could be wrong. I think we should start following the same procedure as for OpenVPN-GUI, that is, update version in sources and add two tags (e.g. 1.3.0.0 and openvpn-2.4_beta2). Thoughts?

@selvanair
Copy link
Copy Markdown
Collaborator

Yes, file properties show 0.0.0.0. I have no idea how to get the version into the exec. That said it would be nice to have version/build update and tags matching each release..

@mattock
Copy link
Copy Markdown
Member Author

mattock commented Nov 29, 2016

I'll look into getting the version number to File properties, and then force-push new stuff to this PR.

This commit adds assembly metadata such as product version (now 1.3.0.0). This
information will be shown in File -> Properties dialog in Windows Explorer.

Signed-off-by: Samuli Seppänen <samuli@openvpn.net>
@mattock
Copy link
Copy Markdown
Member Author

mattock commented Dec 21, 2016

@selvanair : with the force-pushed changes the version numbers show up properly in File Properties -> Details. The only field I was unable to populate was "File description". A test build is here:

Right now the version number is defined in five different places. This should be improved at some point.

Setting the language field would have afaict required setting up satellite assemblies, i.e. localized AssemblyInfo files for each localization (e.g. en-US). I don't think that is worth the effort for openvpnserv2.

Comment thread OpenVpnService.sln
# Visual Studio 14
VisualStudioVersion = 14.0.24720.0
MinimumVisualStudioVersion = 10.0.40219.1
# Visual Studio 2012
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like MonoDevelop (which I use) and Visual Studio (used by someone else) are fighting each other here. I can revert this change if necessary.

@selvanair
Copy link
Copy Markdown
Collaborator

I too use mono, so wouldn't care about this visual studio version change..

@mattock
Copy link
Copy Markdown
Member Author

mattock commented Dec 27, 2016

@selvanair : Ok, so I take that as an ACK?

@selvanair
Copy link
Copy Markdown
Collaborator

OK, checked the executable. Looks good. We have to just remember to update the version number (1.3.0.0) in two places (in AssemblyVersion.cs and the .csproj file).

ACK.

@mattock mattock merged commit 22e23e5 into OpenVPN:master Dec 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants