Thank you for quick response. Question answered.   ... View more

API TESTING is a software testing type that validates Application Programming Interfaces (APIs). The purpose of API Testing is to check the functionality, reliability, performance, and security of the programming interfaces. In API Testing, instead of using standard user inputs(keyboard) and outputs, you use software to send calls to the API, get output, and note down the system's response. API tests are very different from GUI Tests kgtopg and won't concentrate on the look and feel of an application. It mainly concentrates on the business logic layer of the software architecture. ... View more

Hi All I just wanted to refresh this thread as I could not come up with a solution but seen the same issue on another website: http://www.appdeploy.com/messageboards/printable.asp?m=48183 Any help is appreciated! ... View more

Thanks Debbie ... View more

No UAC window is, expectedly, prompted up to this point, hence nothing was accepted. I remember that, in the log file, it shows the USERNAME property is resolved to "user" instead of "std". I can re-create and provide the logs tomorrow AM first thing if that would help. Thanks Michael. ... View more

To be honest, I am not sure about the internals of the driver installation. The driver comes with a merge module and there is a Custom Action called InstallDriver. At the point where this CA is executed, following window is displayed. Thanks for the reply and looking forward to more 🙂 ... View more

From the "Standalone Build" topic: The Standalone Build can coexist with other versions of InstallShield, InstallShield DevStudio, or InstallShield Developer. Standalone Build files from different service packs of InstallShield, InstallShield DevStudio, or InstallShield Developer can coexist on the same machine (in different folders). ... View more

Hi I am facing a similar problem too. I have created an install script msi project in install shield professional 12. As Michael mentioned, the dialog is displayed with Install and cancel buttons. But clicking on cancel does not abort the process, the dialog is displayed infinitely ... View more

Customer says that issue is not presenting itself after a reboot. Thanks Robert. ... View more

No, I could not find a solution for that... I ended up with statically linking the dlls. ... View more

Thanks, I will try this and see if this is the reason why it is getting included. I am not sure if this scan feature of InstallShield is really a good thing or a bad thing. It is including files without me noticing... If there is really a necessary file then I should include it myself explicitly. Say it finds a dependency on a COM dll.. As far as I can see, InstallShield will chose to self-register the file. Then it is violating the best practice which may result in failure on a client installation. If I dont read the logs or dont investigate the resulting MSI always... ... View more

BuildErrorCount is actually enough.. I want to return some error code if the build is returning some errors. So I can use the BuildErrorCount. Also, is it possible to retrieve the errors from the automation script? I know the errors are written to the build logs but is it also readable from the automation interface. If yes, I would print them in our master build logs. Thanks. ... View more

Beyond that uninstaller information, there's cached product information under HLKM\Software\Microsoft\Windows\CurrentVersion\Installer and in the cached MSI database. I don't know from memory which set of data the Windows Installer engine uses for comparisons (presumably it would be the same everywhere), but in any case I'm pretty sure it's undocumented, so doing anything directly with it is probably a bad idea. The good news is, there are MSI API functions to get information about installed products, too. ... View more

Correction - You should be able to call MsiProcessMessage (or Session.Message) with INSTALLMESSAGE_FILESINUSE to add information to FilesInUse. I hope this helps. Thanks, Alpesh ... View more

Correct, it is not. There is a physical location but it's private to the Fusion API that manages the GAC. Drop to a dos prompt and CD to the Windows\Assembly directory and dir a dir /s foo.dll and you'll start to learn how the GAC's single instance storage works. Now for the life of me I can't imagine why you would need a registry value that points to the location of the DLL. If a .NET assembly needs your DLL it simply references it per the assembly name, version, culture and public key token and .NET will serve it up for you. It's intentionally abstracted. ... View more