Please make up your mind
I download nightlies and place the new one on top of the old one because I can keep my custom workspace and reuse the shortcut. The problem is that sometimes the new nightly is called nightly.exe and sometimes it's called MuseScore3.exe. It would be nice to know that when I replace a nightly with a nightly I won't be running the old one. In OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4370, revision: 29165bb the nightly was called MuseScore3.exe, in the last one I downloaded (OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4482, revision: 2e2af50) it was called nightly.exe. This isn't the first time this has changed.
Comments
They should've all been nightly.exe. A script was missed when creating the first beta3 builds to correctly rename this file.
This was fixed almost right after the first build you've now mentioned. It happened in https://github.com/musescore/MuseScore/commit/a71c61ce1c9f8ac67b5d91d62…
@mike320, previously double-clicking nightly.bat (in the base directory of the nightly .7z) wouldn't work, because of a change in name of "musescore.exe" as the name of the built exe into "MuseScore3.exe" for regular building. But when that name was changed, someone forgot to change the appveryor after_build script to rename that resulting exe into nightly.exe. A recent PR (https://github.com/musescore/MuseScore/pull/4360) has fixed that after_build script to now rename the built "MuseScore3.exe" into "nightly.exe", which now allows the nightly.bat file to work correctly.
So basically the mind has been made up now.
Oh wow, that explains the complete lack of fixes that I was scratching my head about lol. Why is there even a MuseScore3.exe in the nightly? Seems confusing.
In reply to Oh wow, that explains the… by Laurelin
This was used by accident for a short time as explained by someone else. You can delete it from your nightlies folder to prevent confusion. If you see it again, I guess that means the mistake was made again.