en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en nl en en en en en en en en de en en en en en nl en en it en en en en mwl en en en en es en en en en en en en en es en en nl en nl en en en en en en en nds en hu en en en sv en en en en nl en en en en en en en en de en en en fr en en en en en en en en en pt en en en en en en
By logging into your account, you agree to our Privacy Policy, personal data processing and storage practices as described therein.
Forgot password or user name?
Search in titles only Search in PowerBASIC for Windows only
You are not logged in. You can browse in the PowerBASIC Community, but you must click Login (top right) before you can post. If this is your first visit, check out the FAQ or Sign Up.
All Time Today Last Week Last Month
All Discussions only Photos only Videos only Links only Polls only Events only
Join Date: Oct 1999
14 Mar 2000, 11:31 AM
I don't know if this question really belongs on this board, but when creating a program that will have future updated versions, is there a special trick? Or do you just have the new version overwrite the old version? What do you pro's do?
PowerBasic Racing Simulator (October 2007 clip - 15.1MB wmv file) http:http://www.performancesimulations.co...m-GenIV-12.wmv
Join Date: Feb 1999
14 Mar 2000, 11:44 AM
I have an opinion on this.
I prefer to "never" release a new version of a program with the "same" name if possible. This can cause problems when an older version overwrites a new one.
Now sometimes, it may not be a problem, but if it can be avoided, this is good.
What I like to do is embed the version number in the filename , so the filename changes as the version changes. This is really important if you sell programming tools in DLL form.
This makes it easy to figure out which version is which and also saves your customers some grief.
An example of NOT doing this that has caused much grief, is the VB 5/6 runtime DLLs. Microsoft has multiple service packs (upgrades) of each one (3 upgrades for VB 5), but they all use the same DLL name.
Many a VB app has installed the "old" version over the new one and then some VB apps won't run.
14 Mar 2000, 12:26 PM
What I do when upgrading one of my apps, is to make sure it is installed as an UPGRADE only, overwrite all of the main program files etc. and maybe have an accompanied program to clear up and convert some of the old file formats.
I also think including a repair utility is a good thing with some programs, such as in IE5.
That way if anything goes wrong with the program, the user has a way to 'repair' the application settings and restore executables.
Other than that, or for much larger applications, I use chris' idea.
Join Date: May 1999
14 Mar 2000, 01:08 PM
You may (or may not) have noticed that PowerBASIC tools install themselves into separate folders where the version number of the product is part of the name of the folder into which the application is installed. Thus, you can have simultaneously installed and operational, without overwriting previous versions, PB/DLL 5, PB/DLL 6, PB/DLL 7...
If you try to make something idiot-proof, someone will invent a better idiot.
Copyright © 1998-2022 PowerBASIC Tools, LLC - All Rights Reserved.
Powered by vBulletin® Version 5.7.0
Copyright © 2022 vBulletin Solutions, Inc. All rights reserved.
All times are GMT-5. This page was generated at 01:28 AM.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, and to analyze site activity. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.