Switch installed dotnet-tools when changing current dotnet version #41
Description
I've run into a problem that the dotnet tool I wrote and am using is compiled to target a particular .net sdk, but when switching folders and tool-versions the right sdk for the global tool is not always available.
I'm not sure if it's possible to make the tool work regardless of what sdk is available, it might be possible to target dotnet standard perhaps for broad compatibility.
Regardless, I wondered if it would make sense to segregate the installed global dotnet tools to align with whatever dotnet version / sdk is currently active, and have asdf switch the current set of tools as well as the dotnet runtime.
At this point I'm not sure how sensible an idea this is, or if the correct answer is that the tools should just work on all versions of the sdk.
If we did it I guess we'd have to shuffle the global tool install folder around, maybe with symlinks so that the tool installer is unaware that they have been switched around and can just carry on installing into its default path.
Thanks again for the tool, and again, I'm not expecting anything here, just sharing some thoughts while I have it all in my head so perhaps we can build on it.