Android Question Fear of Updating...Ha

[cougar]

I've been a user since 2014. My last update was V8.0. I have written 2 large apps in B4A that I use in my day to day job. I continue to modify them but I am finally beginning to run into issues when trying to run example projects, etc. I get the Maven error, etc. I've read numerous threads and I haven't corrected that yet. It's not a problem for my own apps but trying to implement new features does raise that issue. I also recently discovered my dialogs no longer worked after the upgrade to build 33. I simply hard coded what I needed to avoid having to search for a file to import via the dialog. Works for now. Ha.

Anyway, I would like to update to the newest version but having gone through the VB fiasco from the mid 2000's, I am fearful that I will open my apps and find numerous errors that won't be easily corrected.

I'm just curious what this has been like for others. Do you have older versions of apps that still open/work in the newest version of B4A? And, if not, are the changes fairly simple to implement?

Just curious what others have experienced. And, I know Erel will say I should've updated long ago. I agree but all was fine so I went with the "if it ain't broke don't fix it" philosophy. Lol. Really wanting to rewrite my apps now (from the ground up) and take advantage of the newer possibilities but would still like to be able to make minor changes, as needed, to the older versions without having to reinvent the wheel.

Anyway. Just interested in the experience of others. The good, the bad, and the ugly. Thanks!

 

[RB Smissaert]

I've been a user since 2014. My last update was V8.0. I have written 2 large apps in B4A that I use in my day to day job. I continue to modify them but I am finally beginning to run into issues when trying to run example projects, etc. I get the Maven error, etc. I've read numerous threads and I haven't corrected that yet. It's not a problem for my own apps but trying to implement new features does raise that issue. I also recently discovered my dialogs no longer worked after the upgrade to build 33. I simply hard coded what I needed to avoid having to search for a file to import via the dialog. Works for now. Ha.

Anyway, I would like to update to the newest version but having gone through the VB fiasco from the mid 2000's, I am fearful that I will open my apps and find numerous errors that won't be easily corrected.

I'm just curious what this has been like for others. Do you have older versions of apps that still open/work in the newest version of B4A? And, if not, are the changes fairly simple to implement?

Just curious what others have experienced. And, I know Erel will say I should've updated long ago. I agree but all was fine so I went with the "if it ain't broke don't fix it" philosophy. Lol. Really wanting to rewrite my apps now (from the ground up) and take advantage of the newer possibilities but would still like to be able to make minor changes, as needed, to the older versions without having to reinvent the wheel.

Anyway. Just interested in the experience of others. The good, the bad, and the ugly. Thanks!

Just keep the old app running as it is and slowly start building the new one.

RBS

 

[cougar]

Yeah. That would be the plan. It's just that I use the apps and just had to make some changes this week. My fear is that if I upgrade to V12 the next time I open the project I will be hit with numerous errors, etc. I suppose I could keep v8 on one computer and put v12 on another one just in case. I guess since it's now free that wouldn't be a license issue. Although my attempt to download the newest version hasn't been successful so far. Probably because I'm using Bing at the moment instead of Chrome. Gives me warnings and doesn't appear to fully download. Another issue to deal with. It never ends. Ha

 

[emexes]

I suppose I could keep v8 on one computer and put v12 on another one just in case.

That's what I did, in order to keep the Java SDK versions aligned too. Great minds think alike?! ?

I keep meaning to investigate doing it better by using virtualisation, but for my limited requirements the juice isn't yet worth the squeeze (or: if it ain't broke, don't fix it) and so I haven't gotten around to it, but... surely somebody here has already done that and could point us in the right direction.

 

[cougar]

Yep. I've just grown tired of watching the product grow while I sit here in the dark watching. Lol. These aren't small apps though. Probably 800+ pages of printed code for one. Maybe 500 for the other. A lot of that is because I was extremely redundant in the early stages. The other is that I got in the habit of blocking/commenting out old code when I did updates, but was too afraid to delete it. Lol. Now, I just want to start fresh and rewrite everything with the newest available resources...so I can do the same thing again in a few yeas with version 17 or something. Ha.

 

[cougar]

By the way...the Edge browser was my issue on trying to download the newest version. It worked fine with Chrome.

 

[cougar]

Did the update to version 12. No issues. A few warnings about msgbox's but no errors. Compiled slower but completed and works fine on the old Samsung 3 tablet I put it on. I was afraid for nothing. Plus, now all of the examples I've been wanting to run are working. No Maven errors or other sdk issues. I promise to stay updated from now on. Lots to learn now as I open my mind up to newer features/coding changes, etc.