Upgrade process

[khodges747 55]

@@Luke,

For many weeks now I've been politely imploring You (the Royal You, meaning the development team) to allow users the option of upgrading to new versions of MBT.

 

That still hasn't happened, and sad to say, with almost every new version of MBT there is a problem that I frankly don't think we need to live for the time it takes until You (still the Royal You) fix it. 

 

To be honest, you're being arrogant by assuming your clients will put up with annoying errors. I have a lot of respect for you and the development team. I love your product. But I hate that you put me through so many unnecessary inconveniences every time there's an upgrade that I don't particularly want or need.

 

Just give me the option to remain on the version I already have. You do it with MB Server, so you can do it with MBT, too.

 

Please.

 

Thanks.

 

P.S. My MBT 2.6.5 still won't shut down correctly with Windows shortcut keys. My MBT 2.5.40 was working perfectly before it got automatically upgraded to the version that's broken.

[Luke 36998]

Thanks for the feedback, we will get that resolved.

[khodges747 55]

@@Luke, with all due respect, that's not an answer to my complaint.

 

I know you'll fix the problem with incorrect shutdown.

 

What are you going to do about the version upgrades? Concrete answer, please.

[Luke 36998]

As far as the update process goes, the app is built with a mixture of hosted components as well as installed components. The hosted components are updated automatically by our embedded instance of Chromium, and it very nicely supports running both with and without an internet connection.

 

What makes your request tricky is that we would have to change the way we've built the app, and I like this model. You can stop the installed components from updating if you wish, there is a system.xml config file just like the server and you could set EnableAutoUpdate to false. But that will not stop the hosted components from updating, and anytime there is an update that affects compatibility, you will not be getting those updates.

[Luke 36998]

Alt-f4 is resolved for the next update to the app. Thanks !

[khodges747 55]

Thanks for the concrete answer.

 

You may like the model you've developed, but if it's causing problems for your clients, then changing it is something to consider.

 

I'll change the EnableAutoUpdate to false when the current shutdown problem is fixed.

 

Edit: An alternative is to allow users to find and install an older version of the program. Then if update 2.6.7 annoys me, I can go back to a version I had before.

Edited May 8, 2017 by khodges747

[Koleckai Silvestri 1150]

Interestingly enough, I've always wanted a button to upgrade. Currently, it is running 2.5.38 on my computer and just gives a blank screen for about 5 minutes before anything shows. I see by other posts that the current version is 2.6.4. I don't think it will auto-upgrade to that version either.

[Luke 36998]

Interestingly enough, I've always wanted a button to upgrade. Currently, it is running 2.5.38 on my computer and just gives a blank screen for about 5 minutes before anything shows. I see by other posts that the current version is 2.6.4. I don't think it will auto-upgrade to that version either.

 

In your case (and others), the installation is massive, around 130mb, primarily due to the bundling of x86 and x64 together. Between the downloading and then unzipping of all the files this is causing the update to not happen at all when it doesn't complete in a certain amount of time. It is on my to do list to rework this and separate them into two downloads.