The disadvantage of running TSF_dotNET.exe directly from a network share is that it will be impossible to replace the Windows GUI's binaries while it is in use by anyone. TSF_CS.exe circumvents this problem by copying the binaries of the Windows GUI to the user's AppData folder before running it from there.



However, the AppData folder should not grow endlessly when using TSF_CS.exe. TSF_CS.exe will always copy the Windows GUI's binaries to a folder with the same name as the folder on the network share. In doing so, it will overwrite the files at the target location, meaning that the size should always remain roughly 300MB. The only reason for the AppData folder to grow endlessly is that the name of folder containing the Windows GUI binaries on the network share is changed every time it is replaced by a new version. The best practice here is to replace the binaries in the folder, rather than deleting the folder and replacing it with a new one.

---

In such deployment scenarios it's a good idea to use the CachePath extended property. In the latest release (2018.3.18), environment variables such as %USERPROFILE% and %LOCALAPPDATA% are properly resolved.



See also: Extended properties - Thinkwise Docs

---

Hi ​@Henk Nicolai ,

Do you know if the CachePath extended property can still be used?

We try to make a terminal server setup, without ClickStart, and we want to save the application in a read-only folder and need the Cache data to be saved in a User folder.

I have added a CachePath record in the Extended Properties with a value %LOCALAPPDATA%\Thinkwise\TEST\Cache

For some reason cache data is still saved in the in the application folder. Can you explain this?

 

---

Hello Harm,

I have confirmed that CachePath still works, as well as adding placeholders for environment variables to it, such as %LOCALAPPDATA%. If this is not the case, it is best to create a ticket in TCP.

Best regards,
Henk

---