Options/General - Store caches in other custom folder.

There is setting Store caches in (1) system TEMP folder; or (2) solution folder; in the Options/General. Is there possibility to set some other custom defined folder?

7 comments

Hello,

There is setting Store caches in (1) system TEMP folder; or (2)
solution folder; in the Options/General. Is there possibility to set
some other custom defined folder?


No.

What is your scenario?


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

(1) Temp folder is for me generally bad, because windows cleaning tools like for example cleanmgr.exe (or other 3rd party tools), clean the temp folder by default and then caching storage for ReSharper will be destroyed.
(2) If the ReSharper cache is in the solution folder, then for example my backup procedure which saves the solution folder, saves already ReSharper cache within the solution, and this is not necessary to back it up. This is a mess within the solution folder.
=> Therefore any other custom folder can be the best solution to store ReSharper cache. The very GOOD solution have you already used in the IntelliJ IDEA, where can I set the idea.system.path in the file idea.properties, which is used to store some IDEA caches. The equivalent possibility may be nice in ReSharper.

0

Hello,

(1) Temp folder is for me generally bad, because windows cleaning
tools like for example cleanmgr.exe (or other 3rd party tools), clean
the temp folder by default and then caching storage for ReSharper will
be destroyed.


Hopefully this is no much problem, as R# can restore the caches promptly.
Unless you're using the Solution-Wide Analysis feature, in which case it
might take some considerable amount of time.

However, the schedulled cleanup is the only reason we have this option for
storing caches in %TEMP% OFF by default, so there is, indeed, a problem.

(2) If the ReSharper cache is in the solution folder, then for example
my backup procedure which saves the solution folder, saves already
ReSharper cache within the solution, and this is not necessary to back
it up. This is a mess within the solution folder.


If you mean the source code control systems, which is a usual means for backing
up the source code, then this folder could easily be excluded from source
control, just like the .ncb file for example, which is the same thing to
Visual Studio as cache folder is to R#.

=> Therefore any other custom folder can be the best solution to store
ReSharper cache. The very GOOD solution have you already used in the
IntelliJ IDEA, where can I set the idea.system.path in the file
idea.properties, which is used to store some IDEA caches. The
equivalent possibility may be nice in ReSharper.


We'll evaluate the possibility of adding such an option, though it seems
like it's not a popular request. By the way, you could do a similar thing
to Visual Studio as to IDEA, I mean, assign the TEMP folder to a different
location for the Visual Studio process. To some extent, this is going to
work the problem around even on the current R# version.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

you wrote: "assign the TEMP folder to a different location for the Visual Studio process"
I'm asking: how to do it?
I did not found any option in visual studio nor find some information about it in internet.

0

Hello,

you wrote: "assign the TEMP folder to a different location for the
Visual Studio process"
I'm asking: how to do it?
I did not found any option in visual studio nor find some information
about it in internet.


There's no end-user setting for that in Visual Studio.

One way is to modify the environment in the parent process of Visual Studio
before starting the Visual Studio process itself, so that it inherits the
modified PATH setting. For example, you could do SET TEMP=c:\somefolder in
the console before running devenv.exe from it — and that could be done by
a batch file (.cmd) that starts DEVENV. That would be a typical thing to
do in a multicompiler environment where different processes should have different
sets of environment variables. Alternatively, that could be a simple C# program
to call System.Environment::SetEnvironmentVariable for TEMP and then System.Diagnostics.Process::Start
for DevEnv.exe.

Another way is to do the same on Visual Studio startup, for example, in a
macro.

A crude workaround of course, but that's all we've got for your scenario
against the current version of R#.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Please sign in to leave a comment.