The 2.0.x portable apps can't run in parallel with a nightly (or self) build, 3.0.
The full 2.0.x app, can run in parellel with 3.0, as can the 1.x portable apps.
Why? 1.x, 2.0 and 3.0 can run at the same time, but 2.0 prtable app can not rund together with 3.0 (it can with 1.x though), this clearly is a bug or at least serious restriction to me or bad design?
Either an user runs portable (one version only!) or local MuseScore.
There is no good reason to run both at the same time.
If you would run both the portable launcher couldn't distinguish which changes to registry and file system have been made by local or portable version. Clean-up wouldn't be possible.
X.x portable shouldn't be run with X.x local!
It works in some cases because MuseScore developers changed the name of executable.
As said 2.0 portable does not run together with 3.0 nightly, but should
Just like 1.x portable runs with 2.0 local and vice versa
Hmm, hold on a sec, program name? It is MuseScore.exe in either case. But 2.0 local and 3.0 local can run at the sdame time, so they do have different means to detect the other
I'm not complaining that X.x portable does not run with X.x local, if X is identical, but that they don't run together when one X is 2 and the other is 3
Comments
Not a bug, it's a feature.
Why? 1.x, 2.0 and 3.0 can run at the same time, but 2.0 prtable app can not rund together with 3.0 (it can with 1.x though), this clearly is a bug or at least serious restriction to me or bad design?
1.x portable can't run with 1.x local.
2.x portable can't run with 2.x local.
3.x portable won't run with 3.x local.
So far so good and OK, but 2.x protable doesn't run with 3.x nightly local either, that's my complaint
Either an user runs portable (one version only!) or local MuseScore.
There is no good reason to run both at the same time.
If you would run both the portable launcher couldn't distinguish which changes to registry and file system have been made by local or portable version. Clean-up wouldn't be possible.
X.x portable shouldn't be run with X.x local!
It works in some cases because MuseScore developers changed the name of executable.
As said 2.0 portable does not run together with 3.0 nightly, but should
Just like 1.x portable runs with 2.0 local and vice versa
Hmm, hold on a sec, program name? It is MuseScore.exe in either case. But 2.0 local and 3.0 local can run at the sdame time, so they do have different means to detect the other
And again:
X.x portable shouldn't be run with X.x local!
Otherwise portability is broken. Use local versions instead for your testing.
I'm not complaining that X.x portable does not run with X.x local, if X is identical, but that they don't run together when one X is 2 and the other is 3
Seems it depends on the order they get started.
Start 2.0.x portable, then 3.0 local: works
Start 3.0 local, then 2.0.x portable: does not work
1.x and below have mscore.exe, 2.x and above have MuseScore.exe
As said, it works one way but not the other, doesn't make sense to me. local 2.0 vs. 3.0 doesn't have that issue