[BUG]: The `.tool-versions` file does not switch automatically when it exists under windows powershell.

[nadirvishun]

Version
0.9.1
OS
Windows 11

Describe the bug

• When switching to a directory containing the tool-versions file in PowerShell, it does not automatically switch; tested with both Java and Node.js, neither worked.
• The Invoke-Expression "$(vfox activate pwsh)" has already been configured in Microsoft.PowerShell_profile.ps1.
• Strangely, when running vfox list java, the arrow points to the switched version, but the switch did not actually take place

Screenshots[optional]

• Microsoft.PowerShell_profile.ps1:

  

• .tool-versions:

  

[Im-SAMW]

我也有同样的问题，刚装上vfox时是正常的，突然有一天就不行了，需要自己手动切换版本；

还有，打开powershell窗口，首次使用java命令很慢；

[rsenna]

Possibly related: vfox use -s tool@version does not work on powershell (on windows 11).

Tested on vfox v0.9.2 - the original issue described by this PR still happens on powershell using v0.9.2 btw.

[rsenna]

Just a wild guess: I noticed vfox activate pwsh works by changing the powershell prompt.

And maybe that doesn't work for me (us?) because I use a custom prompt tool - namely https://ohmyposh.dev/...?

Anyway, a better approach for running code on directory change, for modern powershell 5+, would be using the LocationChangedAction event handler instead.

I'm new to vfox and I'm still setting it up on my environments, but I might fork it and test this approach (if I have the time).

[aooohan]

Please upgrade to v0.10.0, which has fixed this issue.