Default move-delete fails on non-default Windows drive about dotnetcleanup HOT 6 CLOSED

That's what I started building yesterday 😃 Maybe I can test it and get it out today.

from dotnetcleanup.

Version 0.6.0 has been deployed to Nuget:
https://www.nuget.org/packages/dotnet-cleanup/0.6.0

It could be awaiting package validation and indexing at this very moment, but should be public soon.

from dotnetcleanup.

Thank you for bringing this up, @amis92. Could you provide the full stack-trace of the error and I can look into how to maybe solve it or at least have a more user-friendly UX?

from dotnetcleanup.

I could, but a bit later. However, the solution is given in Stack Overflow linked: if the volumes differ (of the cleanupPath and movePath), you can't use Move at all. Either copy-remove the directory, just remove the directory, or throw a (more?) friendly error message.

I'd honestly prefer any solution that doesn't throw. A warning, maybe.

from dotnetcleanup.

Half the point of the tool is that it moves the files before deleting them, letting you move on with your work. I'll come up with a solution to work around it :)

from dotnetcleanup.

Then I'd suggest a temporary folder somewhere nearby target folder, on the same volume. It's deleted in the end anyway, right?

from dotnetcleanup.