Home: Consider moving the .nuget directory on Windows to a subdirectory of %AppData%

[pranavkm]

On Windows, everything under the Users directory with the exception of the AppData sub directory is indexed. Consequently restoring packages kicks off the search indexer. It doesn't look like it's actually indexing package contents, but it does index the file names. Moving it would avoid all the extra work.

For past discussions, see aspnet/dnx#1507 and https://github.com/dotnet/cli/issues/591

[MicahZoltu]

Users/<username>/.nuget is also against Windows convention as defined by Microsoft some number of years ago. The issue mentioned by @pranavkm is a technical reason not to store the files here, but I believe the user expectations reason is also important and Windows users expect cache data like this to be in %LOCALAPPDATA%.

Not only will moving this prevent indexing, but it also allows users to redirect where these cache files go. By not following the Windows convention you break user workflows where the user has their user directory on a network drive and %LOCALAPPDATA% on a local disk.

[youngdelaney]

we need to concert

[emgarten]

NuGet now supports several ways to set the packages folder location.

I haven't seen a lot of feedback around this the options to set the path were added. I'm going to close this issue as wont fix unless there is still a need for this.

[MicahZoltu]

I would still argue strongly that the current _default_ location is being a really bad citizen on Windows since the NuGet cache can grow incredibly large and should _not_ be indexed/roamed across a network. Having options to redirect it is definitely a big improvement, and provides people who care about their OS remaining healthy an option for resolving the problem. However, I do believe that this issue should be investigated and addressed _eventually_.