Skip to main content

Extended properties | Thinkwise Documentation

The entry CachePath has a neat little entry:

A custom path where the Windows GUI stores a cache of the application definition to increase the startup time. 

My best bet is that this is something you would not like to set, because, well, it increases your time waiting on starting up the app right?

 

Now to my probable problem: We’ve got it set to %temp%\awesomeness_app 

That location is not restricted for reading, writing etc… Can it be that for some time now this is not working anymore, because it (tries to) write its cache in the same directory as where the executable is stored?

 

Hi Ricky,

We have released a hotfix yesterday afternoon as we found out that the procedure responsible for returning global configuration extended properties would not return the data of the default global configuration when no global configuration ID was specified. This has been fixed.

If you did specify a “globalconfiguration” in the INI, this hotfix does not change that behavior, it only changes for when none was specified in the INI. If ou are using the Windows 3-tier GUI, a new GUI version (2025.1.13) is required as well. Windows 2-tier GUI is compatible as-is.

I did contact you through the ticket you've raised about this topic with the same information, so I share the same answer here for our fellow Comunity members.

Thanks ​@Mark Jongeling, it works as expected again. But it still should decrease the startup time, not increase it right?

Reply


Terms & ConditionsCookie settings