This is the legacy 4D documentation web site. Documentations are progressively being moved to developer.4d.com

Home

 
4D v20
CS
ShareLocalResourcesOnWindowsClient

ShareLocalResourcesOnWindowsClient  


 

 

/ Preferences4D / BuildApp / CS / ShareLocalResourcesOnWindowsClient

True / False

This key defines if the local resources of the application must be downloaded from 4D Server to a shared folder on Windows merged clients. Local resources include all files needed for application execution on the client side (.4dz file, Libraries folder, Resources folder...).

When set to False (default), local resources are downloaded in the user folder:
\Users\{UserAccount}\AppData\Local\{ApplicationName}\{ServerInformation}_ClientFolderSignature\

When set to True, local resources are downloaded in a shared folder:
\ProgramData\{ApplicationName}\{ServerInformation}_ClientFolderSignature\.

With a Remote Desktop Service or Citrix environment, using a shared folder for 4D local resources allows saving downloading time and disk space. 

Compatibility Note: This key is only taken into account in the following context:

  • 4D project
  • merged client application on Windows

When this key is set to True, updating client applications requires that users have a read/write access to the ProgramData folder. We recommend that an Administrator follow these steps in this context:

  1. Disconnect all users and forbid user access to the merged 4D client application to update.
  2. Update the 4D Server merged application.
  3. - If automatic client update is activated: in the Windows Remote Desktop Server Administrator session, launch the merged 4D client application and follow the update process. At the end of the process, the 4D Client merged application will be launched and connect to the 4D Server merged application, and then perform automatic local resources updates in the shared folder.
    - If automatic client update is not used: in the Windows Remote Desktop Server Administrator session, update manually the merged 4D client application and launch it to connect to the 4D Server merged application and perform automatic local resources updates in the shared folder.
  4. Restore users access to the merged 4D client application.

These steps will make sure that users are not launching several instances of the merged 4D client application, avoiding concurrent writings to the shared local resources or writing rights errors.

 
PROPERTIES 

Product: 4D
Theme: CS

 
PAGE CONTENTS 
 
HISTORY 

Created: 4D v19 R7

 
ARTICLE USAGE

4D XML Keys BuildApplication ( 4D v20)