Portable version = A portable/standalone version is available.
Free Trial version available for download and testing with usually a time limit or limited functions. Trialware = Also called shareware or demo. It may be disabled when installing or after installation.
Free software Ads = Free Download software and open source code but supported by advertising, usually with a included browser toolbar. Freeware Ads = Download Free software but supported by advertising, usually with a included browser toolbar. Free software Trialware = Download Free software and also open source code but some parts are trial/shareware. Free software = Download Free software and also open source code also known as FOSS (Free and Open Source Software). Freeware Trialware = Download Free software but some parts are trial/shareware. RECENTLY UPDATED = The software has been updated the last 31 days. NO LONGER DEVELOPED = The software hasn't been updated in over 5 years. Type and download NO MORE UPDATES? = The software hasn't been updated in over 2 years.
Version number / Beta version number / Update version number and when it whas released. Just a generally workable web installation method for a simple and small windows based app.Explanation: NEW SOFTWARE= New tool since your last visit NEW VERSION= New version since your last visit NEW REVIEW= New review since your last visit NEW VERSION= New version Latest version Bottom line is that I don't need anything very sophisticated, I don’t seem to have a specific question here, but your first post was very helpful so I thought I’d clarify my situation in case you have any further insights or suggestions. I suppose I’d need to provide code signing for each of the three files, the self extractor, the setup.exe and One of the links provided suggests that a self extractor that brings both files down, then runs setup.exe might be a good way to go. Links that the setup.exe takes care of the issue of dependencies. msi is downloaded and placed alongside it. If it’s downloaded standalone same problem, but it will work if the. On the other hand, the setup.exe, when run from the web doesn’t see the. msi in this way has the risk that missing dependencies could cause failure. msi file will result in successful installation whether run from the web or downloaded and run from the local machine. msi file.Įxperimentation shows on a couple of systems (Vista Home, Windows 7 Home) that a web link to the. So I put it together in a VS setup project, generating the setup.exe and.
So it would seem the “one click” install technology is not Now I really don’t want to port the Borland C++ code into VS 2010, I’d end up rewriting the thing, possibly in C#, and to be honest I’ve got better things to do.
I want to install from the web, no CD distribution.
The package consists of an exe, some midi files, and a couple of simple You can believe that… Still runs like a champ on modern Windows systems, but the Installshield product purchased for distribution purposes at the time is long obsolete.
It’s an old executable, built with a circa 1995 Borland C++ compiler, if To put my posting into perspective, I’ve moved into Silverlight browser apps, but still have an old windows program that I’d like to distribute via the web. Thanks much for advices provided, the world hasn’t gotten any simpler and your assistance is much appreciated. This should only be done if you really need the extra control since it is a lot of work, and it can be tricky to get it right. A setup.exe gives complete control over the software configuration An MSI has very specific rules about how it manages the installations, including installing, upgrading, and uninstalling.