moving Nuget_packages as recommeded from the application made nuget unusable, broken visual studio...

[DevTKSS]

trafficstars

Dev Home version

0.1901.687.0

Windows build number

10.0.26100.2605

Other software

OS Build Version: 10.0.26100.2605.amd64fre.ge_release.240331-1435 .NET Version: .NET 8.0.10

Steps to reproduce the bug

let the dev home application move nuget_packages to your devdrive

Expected result

keep the c: clean, move the dev dependencys to the devdrive, no slow down any longer, still working and better performance that was advertised...

Actual result

slow down until moving because of doubled up packages, not longer beeing able to develop on this computer using visual studio because the engine so not find the packages any longer allthought dotnet nuget nuget-Packages -list output was the correct moved path

Included System Information

CPU: 11th Gen Intel(R) Core(TM) i7-1195G7 @ 2.90GHz Physischer Speicher: 15.75GB (9.1GB free) Prozessorarchitektur: x64

Included Extensions Information

Erweiterungen: Microsoft.Windows.DevHome_0.1901.687.0_x64__8wekyb3d8bbwe (Core Widget-Erweiterung) Microsoft.Windows.DevHome_0.1901.687.0_x64__8wekyb3d8bbwe (Hyper-V-Erweiterung) Microsoft.Windows.DevHome_0.1901.687.0_x64__8wekyb3d8bbwe (Windows-Subsystem für Linux-Erweiterung) Microsoft.Windows.DevHome_0.1901.687.0_x64__8wekyb3d8bbwe (Git) Microsoft.Windows.DevHomeGitHubExtension_0.1800.625.0_x64__8wekyb3d8bbwe (Dev Home-GitHub-Erweiterung (Vorschau)) 9932MartCliment.WingetUIWidgets_0.7.0.0_x64__g91dtg5srk15g (Widgets for UniGetUI)

Widgetdienst: MicrosoftWindows.Client.WebExperience_524.30502.30.0_x64__cw5n1h2txyewy Microsoft.WidgetsPlatformRuntime_1.6.1.0_x64__8wekyb3d8bbwe

[Jay-o-Way]

I used this function too. Moved it from C to DevDrive. My experience is that the environment variable (for this new location) was not created, so next time I ran an app it downloaded it all again. Seems to work well after I set the EnvVar. Can you confirm if this is the same for you?

[DevTKSS]

I did check on the variables, those has not been moved, so i did manually and nothing worked anymore. rolled back, it pulled them down again to the regular location, everything fine