René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Unexpected behavior on folders with no projects","articleBody":"I was debugging today a problem with our CI environment on my development machine and noticed a strange bug where the Editor was upgrading randomly, not noticing that my terminal went back to my home folder.\r\n\r\n```pwsh\r\nPS C:\\Users\\mio\u003e Start-UnityEditor -Wait -LogFile build.txt -AdditionalArguments \" -buildPlatform Desktop -buildOutput $PWD\\Build -buildTarget Win64 \"  -ExecuteMethod BuildTools.Pipeline.StartCommandLineBuild -Batchmode -WhatIf\r\nWhat if: Performing the operation \"System.Diagnostics.Process.Start()\" on target \"C:\\Program Files\\Unity\\Hub\\Editor\\2020.2.1f1\\Editor\\Unity.exe -executeMethod BuildTools.Pipeline.StartCommandLineBuild -logFile build.txt -batchmode  -buildPlatform Desktop -buildOutput C:\\Users\\mio\\Build -buildTarget Win64 \".\r\n```\r\n\r\nThat is no bug per-se, the command line utility selects the latest editor (due to the missing `ProjectVersion.txt`). However, the editor still executes fine - because Unity does store the last opened project somewhere (I'm guessing either by registry key or somewhere in `LocalAppData`), and opens that.\r\n\r\n`Start-UnityEditor` falls back to the latest version, starts the Editor, which then opens the last opened project, no matter which `ProjectVersion.txt`.\r\n\r\n## Reproduction\r\n\r\nExecute `Start-UnityEditor` in a folder that does not contain a Unity project\r\n\r\n## Possible Solutions\r\n\r\n`Start-UnityEditor` should either be able to find the folder that Unity is going to open **or** exit prematurely with an error code that this folder is not a Unity project folder.","author":{"url":"https://github.com/mio-moto","@type":"Person","name":"mio-moto"},"datePublished":"2021-02-05T10:02:01.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/222/unitysetup.powershell/issues/222"}