Writing information to the Server Information File (*.tsx)

[hybridspyda]

Hi,

I was hoping that it would be possible to update the Server Information File (*.tsx) that gets uploaded to the server location with custom information. I've tried searching the help file and existing forums but haven't had luck finding a solution.

Is this possible? If so, what would be the best solution for doing this?
I suspect that as it's an INI file, it should be possible?

Thanks in Advance!

[hybridspyda]

Is this not possible then? Or is the forum just inactive?

[Ulrich]

The *.tsx file is a XML formatted file, containing data about the server and client data files stored in the target folder, and this info is used to control if and which file(s) needs to be transferred during the publishing task. It was not designed to be modified or customized with further information, and it is not used by the TrueUpdate client executable. I recommend that you create your own files for storing custom information.

Ulrich

[hybridspyda]

The *.tsx file is a XML formatted file, containing data about the server and client data files stored in the target folder, and this info is used to control if and which file(s) needs to be transferred during the publishing task. It was not designed to be modified or customized with further information, and it is not used by the TrueUpdate client executable. I recommend that you create your own files for storing custom information.

Ulrich

ok, would you be able to give me an example of how to upload a file separate of what TrueUpdate pushes up to a server?

[Ulrich]

TrueUpdate will only upload its own files to the remote server(s), as configured in the "Publish" Settings dialog. If you want to transfer additional and custom files, you can use the "Run After Build" option on the Pre/Post Build tab of the same dialog, and specify a command to upload the desired file(s). You can use a third party command line FTP client, the Windows FTP client (ftp.exe), or even build your own utility with TrueUpdate itself (or Setup Factory, or AutoPlay Media Studio) and the FTP actions to perform the file transfer. If you need consulting/assistance, I would be happy to help - just contact me privately.

Ulrich

[hybridspyda]

Hi, it's been a while and I'm revisiting solutions for this now.

I currently have a PowerShell script that I plan to have "Run Before Build" with particular Command line arguments to construct a manifest.xml which will get uploaded prior to the build process.

Is there a way to feed into the TrueUpdate build process to halt it before it builds in case there's an error that occurs during the PowerShell script process (which I already have pushing out error codes of it's own when it fails)?

[Ulrich]

In this case, it might be best using TrueUpdate from the command line, with a batch file, or a Powershell script to start the unattended build.
First, you could perform the actions you need before the build, if there was no error, then start the unattended build. If there was an error, abort before building. You mention that you are already getting error codes in case of a failure, so changing the flow of the batch or Powershell script shouldn't be an issue.

Ulrich