Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Recommend showing app version number #101

Closed
DavidRieman opened this issue May 27, 2018 · 1 comment
Closed

Recommend showing app version number #101

DavidRieman opened this issue May 27, 2018 · 1 comment
Labels
enhancement help wanted

Comments

@DavidRieman
Copy link
Collaborator

For troubleshooting, it would be helpful if users could report with certainty which version they're using. Maybe we can show the app version number in the settings page or something.

This upvoted answer (not the marked answer) explains how to do this for the ClickOnce apps: https://stackoverflow.com/questions/1098112/how-to-display-clickonce-version-number-on-windows-forms

Alternatively we could use the AssemblyInfo.cs and will have to remember to manually update that every release.
DavidRieman added a commit to DavidRieman/XboxKeyboardMouse that referenced this issue Feb 10, 2019
@DavidRieman
Informational improvements and a CPU pegging bug fix.
1df3ea7 
* Fixed main window title from TestForm to XboxKeyboardMouse.
* (Issue fqlx#101) Added dynamic version information to the settings -> info page,
  which will show different strings for ClickOnce version and DL version, as
  they are unfortunately not trivial to keep synchronized.
* Added information about the dead-zoning mouse engine to the info tab, before
  the info about the other mouse engines.
* Added a link to the main github page for additional information, to make it
  easy for users to find it again.
* (Issue fqlx#143) Fixed CPU pegging while not active.
* Prepared a new ClickOnce deployed version including these fixes.
@DavidRieman DavidRieman mentioned this issue Feb 10, 2019
Merged
DavidRieman added a commit to DavidRieman/XboxKeyboardMouse that referenced this issue Feb 10, 2019
@DavidRieman
Informational improvements and a CPU pegging bug fix.
d1e97fc 
* Fixed main window title from TestForm to XboxKeyboardMouse.
* (Issue fqlx#101) Added dynamic version information to the settings -> info page,
  which will show different strings for ClickOnce version and DL version, as
  they are unfortunately not trivial to keep synchronized.
* Added information about the dead-zoning mouse engine to the info tab, before
  the info about the other mouse engines.
* Added a link to the main github page for additional information, to make it
  easy for users to find it again.
* (Issue fqlx#143) Fixed CPU pegging while not active.
* Prepared a new ClickOnce deployed version including these fixes.
DavidRieman added a commit that referenced this issue Feb 15, 2019
@DavidRieman
Merge pull request #149 from DavidRieman/master
0f210b2 
Informational improvements and a CPU pegging bug fix.
* Fixed main window title from TestForm to XboxKeyboardMouse.
* (Issue #101) Added dynamic version information to the settings -> info page, which will show different strings for ClickOnce version and DL version, as they are unfortunately not trivial to keep synchronized.
* Added information about the dead-zoning mouse engine to the info tab, before the info about the other mouse engines.
* Added a link to the main github page for additional information, to make it easy for users to find it again.
* (Issue #143) Fixed CPU pegging while not active.
* Prepared a new ClickOnce deployed version including these fixes.
@DavidRieman
Copy link
Collaborator Author

This feature is in the latest ClickOnce deployment (ClickOnce-v1.1.0.4)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DavidRieman