{"action":"opened","issue":{"url":"https://api.github.com/repos/Lambda3/dotnet-commands/issues/16","repository_url":"https://api.github.com/repos/Lambda3/dotnet-commands","labels_url":"https://api.github.com/repos/Lambda3/dotnet-commands/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/Lambda3/dotnet-commands/issues/16/comments","events_url":"https://api.github.com/repos/Lambda3/dotnet-commands/issues/16/events","html_url":"https://github.com/Lambda3/dotnet-commands/issues/16","id":176382897,"number":16,"title":"Force reinstallation when directory already exists?","user":{"login":"rafanoronha","id":82253,"avatar_url":"https://avatars.githubusercontent.com/u/82253?v=3","gravatar_id":"","url":"https://api.github.com/users/rafanoronha","html_url":"https://github.com/rafanoronha","followers_url":"https://api.github.com/users/rafanoronha/followers","following_url":"https://api.github.com/users/rafanoronha/following{/other_user}","gists_url":"https://api.github.com/users/rafanoronha/gists{/gist_id}","starred_url":"https://api.github.com/users/rafanoronha/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rafanoronha/subscriptions","organizations_url":"https://api.github.com/users/rafanoronha/orgs","repos_url":"https://api.github.com/users/rafanoronha/repos","events_url":"https://api.github.com/users/rafanoronha/events{/privacy}","received_events_url":"https://api.github.com/users/rafanoronha/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-12T14:00:59Z","updated_at":"2016-09-12T14:00:59Z","closed_at":null,"body":"One colleague had this scenario on his machine where dotnet-commands installation failed cause the package directory already exists. Turns out that was followed by an awful `This package does not have a tools directory` error.\r\n\r\nIs there any way we can prevent that kind of failure?\r\n```\r\nInstalling dotnet-commands...\r\nSearching for 'dotnet-commands' on 'nuget.org'...\r\nFound version 0.4.2.\r\nFound version '0.4.2' for 'dotnet-commands' on 'nuget.org'.\r\nSearching for 'dotnet-commands' on 'Foo'...\r\nThere was no version info for 'dotnet-commands' on 'Foo'.\r\nCould not get a version for 'dotnet-commands' on 'Foo'.\r\nSearching for 'dotnet-commands' on 'FooUnstable'...\r\nThere was no version info for 'dotnet-commands' on 'FooUnstable'.\r\nCould not get a version for 'dotnet-commands' on 'FooUnstable'.\r\nLatest version for 'dotnet-commands' is '0.4.2' from 'nuget.org'.\r\nNupkg url is 'https://api.nuget.org/v3-flatcontainer/dotnet-commands/0.4.2/dotnet-commands.0.4.2.nupkg'.\r\nDownloading nupkg from 'https://api.nuget.org/v3-flatcontainer/dotnet-commands/0.4.2/dotnet-commands.0.4.2.nupkg'...\r\nSaving to 'C:\\Users\\foo\\AppData\\Local\\Temp\\tmp7399.tmp'.\r\nDirectory 'C:\\Users\\foo\\.nuget\\commands\\packages\\dotnet-commands\\0.4.2' already exists.\r\nTools dir is 'C:\\Users\\foo\\.nuget\\commands\\packages\\dotnet-commands\\0.4.2\\tools'.\r\nThis package does not have a tools directory.\r\nCould not install.\r\n```"}}
{"actor":{"display_login":"rafanoronha"}}