-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
Add ability to automatically choose correct architecture. (32, 64 bit) #220
Comments
Hi, To understand this problem let's first look at the 3 dnSpyEx distributions: the Why are two different architecture binaries necessary: Implementing the automatic switching is not possible as in the case of the Sorry for the wall-of-text response, if anything is unclear feel free to ask further questions! |
Hi :)
Very interesting. Thank you for the explanation.
Yeah, I think the context menu problem is worth fixing. That's how I mainly open the program; and, since it is so convenient, I think I'm not in the minority with this behaviour.
Kind regards
Edit: What about the double click? Can it somehow choose the rights bits?
|
Good to hear that, I will work on getting the x86 distribution context menu changed to
Double click for |
Could you not make a small third executable (apart from 32 and 64) that acts as a junction/determinator, that is included in both versions (and identical) - so that the handler can always find it even if both versions are installed - which then looks if the file is 32 or 64 bit and finds and finds out if you have the correct version installed? (In case you might have only 32bit, ie)
Then everytime you start one version a registry key is created withe the path to the exec. and the junction app looks it up and loads the file in the correct one or throws error. (key created every start not only at the first, because you might start the program once in Downloads directory and then decide to keep and move it)
Ah, sorry. Wrote too fast. Basically a headless launcher type thing in both archives that handles/determines the file stuffs.
Alternatively, do actually put both versions together, dnspy_32.exe and dnspy_64.exe, have two folders in root for 32 and 64, dnspy_launcher.exe is handling file enumeration and loads respective dnspy exec. (Depends on how many users may only need one version. If too many, just add the launcher to both archives)
|
Problem Description
We have to have both versions installed. Two icons on desktop. Also it is uncertain with which version the context menu entry will open the file.
Proposal
Combine both and switch automatically to correct architecture needed for file.
Alternatives
Combine both versions into the same download file and let user start
Additional Context
Since it isn't already implemented, there must be a good reason to keep them separate, right? What is it?
The text was updated successfully, but these errors were encountered: