FileManager

This function creates a temporary file on the server with the provided content. It must be deleted by RemoveFileFromServer after it is no longer needed.

To safe disk space, any temporary files are cleaned up when the Across Language Server services are restarted.

This function creates an empty temporary file on the server. It must be deleted by RemoveFileFromServer after it is no longer needed.

This function creates a temporary file on the server with the provided content. It must be deleted by RemoveFileFromServer after it is no longer needed.

To safe disk space, any temporary files are cleaned up when the Across Language Server services are restarted.

The crossAPI implementation of the SOAP interface was changed with Across v7.0 11332. For newer versions of Across, please check the following section of the web.config for the crossAPI service (C:\Program Files (x86)\Across\crossWeb\web.config):

<bindings>
    <basicHttpBinding>
        <binding maxReceivedMessageSize="1048576" />
    </basicHttpBinding>
    <basicHttpsBinding>
        <binding maxReceivedMessageSize="1048576" />
    </basicHttpsBinding>
</bindings>

The value for maxReceivedMessageSize specifies the maximum allowed size of the SOAP message in bytes. The values must be a positive integer.
(Max. value: 2147483647 - note: this is 1 byte short of 2GB)

Please note that the value is officially a 64-bit integer, but we found that configuring a value higher than the value mentioned before results in an Argument out of range exception when parsing the configuration.

Please note that the byte array has to fit the data exactly. All data in the passed array will be written to the file.So filling up the remaining bytes in the buffer with 00 when the buffer is too large for the data will not work. The padding will be written to the file, potentially corrupting it.