Why use shared cache?
There is no more efficient way to increase the scalable performance of applications then the use caching to unload deeper layers.
>> Shared Cache>> Tips and Tricks
Tips & Tricks
Within this section we would like to mention some specific issues we found useful. If you have something useful feel free to send us your report and we will publish it.
A suggestion how to handle old Log Files
Some day somebody complained about to much files. The standard configuration of NLog creates every day new files. We handle this with a simple batch file which takes usage of forfiles.exe. This forfiles.exe is provided within .Net SDK the batch job contains only the following line:
forfiles /p C:\temp\logs\ /d -31 /c "CMD /C del @FILE" /M *.txt
this deletes any *.txt from the directory which is older as 31 day's.
Download forfiles.zip - copy it into your "C:\WINDOWS\system32\" folder and unzip it.
A suggestion how-to handle development log files
in one of the versions we change default log files into the following structure:
C:\temp\logs\client\
C:\temp\logs\notify\
C:\temp\logs\server\
upon development we delete often the files so here you have another suggestion on how you can handle that in a easy way:
@ECHO Clean Logs
forfiles /p C:\temp\logs\client\ /c "CMD /C del @FILE" /M *.txt
forfiles /p C:\temp\logs\notify\ /c "CMD /C del @FILE" /M *.txt
forfiles /p C:\temp\logs\server\ /c "CMD /C del @FILE" /M *.txt
copy this into your root folder: C:\temp\logs as an *.cmd or *.bat file (e.g. cleanlogs.bat) and every time you like to delete all files just execute it instead of browsing.