Updates are an interruption by nature. They arrive on your worst day, they make you close and reopen things, and if one stops halfway you have no idea what broke. So the auto-update in AUTONEST VC was built as something that does not ruin the work you are in the middle of — before it is a way to deliver new versions. On screen it finishes in seconds and you see almost nothing. Here is what is underneath.
The server sends a file list along with a fingerprint (hash) for each one. The program compares those against what is on your PC and downloads only what differs. If three files changed out of twenty-two, three files move. There is no installer to download again, no setup to run again.
If the version matches, it does not even request the list — it stops there. Which is why on most days you never notice an update happened at all.
When files start coming down, a small window appears. It shows how many of how many have arrived, and it has a Cancel button. If you are in a hurry, press it. Everything stops and your existing version starts immediately. No half-downloaded file ends up in the mix.
A cancelled update is not lost. Run it again when you have a moment and it picks up from there.
This is the important one. Downloaded files are not swapped in one by one. They are collected in a staging folder, and only when the last one has arrived are they all put in place together.
If the connection drops, if you close the program, if you press cancel — at that moment zero files have been replaced. Your old version is still whole. The dangerous case is running a calculation on a mix of new and old files, and that case simply does not exist here.
The version number is recorded only after every swap succeeds, so a failed attempt is retried automatically on the next run.
"All or nothing" alone creates a problem. If twenty-one files arrive and one fails, all twenty-one are thrown away. On a slow day that repeats and the update never finishes. That actually happened on one release.
So downloaded files stay in a per-version folder, and the next run fetches only what is missing. The swap still happens only when everything is present, so safety is unchanged — but a flaky connection no longer means starting over.
Each downloaded file is hashed again and compared to the fingerprint the server gave. If they differ the file is discarded. Corrupted in transit, altered on the way, or only half received — none of it gets installed.
The paths an update is allowed to write to are fixed in advance; anything outside that list is ignored even if the server sends it. In particular the plate sizes, thicknesses, flange defaults and other DB values you changed in [Data settings], and the inputs you entered, are never overwritten. When a new version adds items, only the new items are added.
If one update reset your shop's plate list, that would not be an update, it would be an incident. So that place was left out of the list from the start.
You do nothing. Open AUTONEST VC as usual; it fetches when it needs to and skips when it does not. No reinstalling, no re-registering.
There is one reason for all of this. If a tool changes halfway through while you are designing, the whole day's work is in question. An update has to be a thing that does not ruin the work in front of you before it is a thing that delivers features.
Bug reports follow the same flow — straight through, no middlemen.
When a result looks wrong →