Cloning an Existing Remote Repo into a new path disables Clone Button.

[femisimon]

Attempting to clone an existing repo into a folder where the repo has been previously cloned is expected to disable the clone button indicating an error exclamation mark on the path and renaming the folder path where the repo will now be cloned to should re-activate the clone button and allow repo to be cloned. This is currently not happening.

Steps to reproduce

• Launch Visual Studio and Sign-in to GitHub's extension.
• Click on clone and select a repo to clone to the default path '' or a new path set as default.
• Select the same repo to clone; an error exclamation is seen on the link path where repo is to be cloned.
• Rename path to enable cloning of repo.

Expected result - Clone button should be active and allow repo to be cloned.

Actual result - Clone button remains idle.

• GitHub Extension version: 2.0.14.2
• Visual Studio version: 14.0.25424.00