/xmouse-controls

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

Dual target .net-3.5 and .net-4.0 #11

Closed
binki opened this Issue Sep 13, 2018 · 2 comments

Comments

Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
2 participants
@binki @joelpurra
@binki
Contributor

binki commented Sep 13, 2018

On a fresh Windows 10 install, trying to run xmouse-controls shows this:

image

It is possible to build the utility in such a way that Windows is willing to use .net-4.0 to run it: https://stackoverflow.com/a/20865375 . Since this is a simple utility, it would be nice if it listed both SKUs so that it would just work out of the box everywhere without requiring installation of .net-3.5.

I tested the app.config method and it works as long as you have the .config file next to the executable. I will make a PR soon and may investigate if I can do this with the embedded manifest somehow instead of only in the external .config file.

binki added a commit to binki/xmouse-controls that referenced this issue Sep 14, 2018

@binki
Use dual-targeting to run on both .netfx-3.5 and .netfx-4.0+. 
Fixes joelpurra#11.
27df4ce

@binki binki referenced this issue Sep 14, 2018

Merged

Use dual-targeting to run on both .netfx-3.5 and .netfx-4.0+. #12

@joelpurra joelpurra closed this in #12 Oct 6, 2018

joelpurra added a commit that referenced this issue Oct 6, 2018

@joelpurra
Change framework target version to .net v4.0 
- Makes for easier execution on Windows systems without .net v3.5, but has .net v4+. No need for a separate `app.config` there, as it is today.
- Crashes on Windows systems with only .net v3.5.
- Targets application to (primarily) Windows 10, while leaving (primarily) Windows 7 behind.
  - Both are still popular, with a high number of users and large market shares.
  - September 2018:
    - Windows 10: 50.07%
    - Windows 7: 37.2%
- Can both systems be targeted at once, similar to #11/#12 but without `app.config`?

See

- #11
- #12
- https://en.wikipedia.org/wiki/Windows_10#Market_share_and_sales
2a77c92

@joelpurra joelpurra referenced this issue Oct 6, 2018

Open

Change framework target version to .net v4.0 #13

@joelpurra

This comment has been minimized.

Sign in to view
Owner

joelpurra commented Oct 6, 2018

@binki: thanks for looking into this! Long gone is the dream of no version problems in .net ;)

@joelpurra joelpurra added the enhancement label Oct 6, 2018

@binki

This comment has been minimized.

Sign in to view
Contributor

binki commented Oct 7, 2018

Thanks for merging this and building the beta ZIP! I don’t do it happen often, but this really does make configuring a freshly installed Windows 10 VM or machine (which doesn’t have .net-3.5) much easier.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment