Dual target .net-3.5 and .net-4.0 #11
Closed
Labels
Comments
binki
added a commit
to binki/xmouse-controls
that referenced
this issue
Sep 14, 2018
joelpurra
added a commit
that referenced
this issue
Oct 6, 2018
- 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
|
@binki: thanks for looking into this! Long gone is the dream of no version problems in .net ;) |
|
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
On a fresh Windows 10 install, trying to run xmouse-controls shows this:
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.configmethod and it works as long as you have the.configfile 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.configfile.The text was updated successfully, but these errors were encountered: