Auto Upload of Config Files is a Problem

[rkligman]

If I choose to allow TU2 to automatically upload the tc<n> files to their destination where the user app will be looking, every time I make a change to the Server Script it reuploads a new copy of the tc2 file. This in turn causes the Update Client to determine that there is a new Client Data file and asks the user to reboot. So I have to do this step manually. Is there a bug here or ??

I'm using 2.0.3. I don't even need to change anything. Just do another F7 (Build) and all 3 files are updated. I can't figure this one out.

[Mark]

Originally Posted by rkligman

If I choose to allow TU2 to automatically upload the tc<n> files to their destination where the user app will be looking, every time I make a change to the Server Script it reuploads a new copy of the tc2 file. This in turn causes the Update Client to determine that there is a new Client Data file and asks the user to reboot. So I have to do this step manually. Is there a bug here or ??

I'm using 2.0.3. I don't even need to change anything. Just do another F7 (Build) and all 3 files are updated. I can't figure this one out.

Hi rkligman,

It is true the TrueUpdate will upload all three servers files every time you build your project, however if the data in the TS2 file has not changed the TrueUdpate 2.0 client will recognize this and ignore the file.

So if all you change is the server script the TS2 file created should be identical to the previous TS2 file, and no restart will be needed.

But if you change any of the client script, screens, or many or the design-time project settings, a new TS2 file will be generated, which will be recognized by the client, and cause a restart.

[rkligman]

OK. Let me try it again and see that this is true. Maybe I was doing so many things that it looked like an issue that was doing what it was supposed to.