|
Problems with creating a standard Setup for a WinDev 10/11/12/14 Program The problems shown below refer to versions up to WinDev 14! All these problems have been fixed in WinDev v15 ! Unfortunately, the project WDSetup which is delivered together with WinDev 15 is a v15 project and cannot be loaded / changed in previous versions. It will not work to just copy WDSetup.exe, WDInst.exe and WDInst.wdk from WinDev 15 to the appropriate directories of previous versions! Any translations / changes to the project in WinDev 15 only! Cure of severe problems in Windev versions up to version 14: Use Inno-Setup from http://www.jrsoftware.org/isinfo.php - it is free, uses a nifty scripting language, even works with Windows 7, does dual-setups (64-bit + 32-bit), language files for the important languages of the planet are there and many features more. Best of all: It’s totally free. For commercial use too. Problems of WDSetup up to v14 ..Here we’re showing a number of problems / errors when creating a standard setup for a WinDev program. At first we sho a number of screenshots demonstrating the deficiencies. Maybe, in the course of time, we can add some advice of how to overcome these problems or we can even report improvements to the affected software coming from PC Soft! <srProgramFiles> is correct ! Presenting us a <RepInst> while the description doesn’t contain the name is just a cheap trick. Remember: only <RepInst> really works, <SetupDir> will be rejected! The image above doesn’t tell us what’s the <InstDir> or the <RefDir> Another two unknown directories .. The install process is started. At first, since we defined that the HFSQL-Server should installed or updated, the Setup program WDSetup doesn’t find the existing server and wants to install (a secons) HFSQL-Server on this computer. Uh, we can see, it is the ‘old’ place for the HFSQL-Server on a Windows XP system! However, PC Soft installs the HFSQL Server now in \programs (x86)\PC Soft\HyperFileSQL Server as shown in the lower section of the image. Now, the setup program runs into the <SetupDir> which is defined above - and is unable to understand or create it! Just the prove that <SetupDir> is invalid - the BackPrima.wdd which should go into <SetupDir> is nowhere! |