Thanks for the answers. I didn't find /qb! that option in the documentation, but it exactle what I needed. ... View more

For anyone interested... I wrote to the support addresses on the website and got an answer from the support guys in Japan, which proved to be very prompt and professional. I had an old trial account, which was transformed in a productive one. Problem solved 🙂 ... View more

I thought about using Installed property in the "Install Condition" (I use a BasicMSI project). This seams the easiest way to me. However, I didn't find much about building advanced conditions. I want to check if there's already a product installed on the target machine with the same UpgradeCode as the product to be installed. How can I check this? I know that this approach doesn't stop a hacker, but I just want to add another layer of "security". The database creation scripts are only executed on initial install, which is not available to the users, so they won't get much, even if they hack an update. ... View more

Now it works. Thanks. I have one more question about the install conditions: I want a major version setup to install only if there is another install on the machine, having the same UpgradeCode number. I want to prevent the users to download an upgrade if they don't actually have an initial install to work on. ... View more

The releases work fine. There is one case when it's necesary to do a major upgrade (because I have to modify files). I have 2 projects. The 1st project is the initial install, 2nd is the upgrade. They share the same UpgradeCode. I registered both product with FLEXnet Connect. On the 2nd, I created a major version. Then I tried to add a new update on 1st product in FLEXnet Connect, update file being as the 2nd .msi file. I try to test this update, but I got the error: "The Software Manager does not recognize this product. Please contact your software vendor for updates to this product. Error 13003: Version Not Registered with the FLEXnet Connect." Do you know what's wrong? Alina ... View more

I still got some questions. What I did: I created a Basic MSI project that run a script on the DB (the solution is called is called Setup1_1) and ran it. I copied to another project (solution called Setup1_2, same name for the project), changed Version and Package Code and put an extra script in it. What I want to accomplish is make an upgrade, so that when I run it, only the second script will be run on the DB. I added an item under Upgrade Windows Installer Setup with Setup to Upgrade pointing to Setup1_1.msi. I tried to Validate item, but I got an error saying Unable to locate the latest release for validation. I tried to add a new Release, but it didn't work. When I try to run Setup.msi on the second solution I got Another version of this setup is already installed. Installation of this version cannot continue.... If I run setup.exe from the same folder instead I got This setup will perform an upgrade.... If I install, what it does is install both scripts. I tried with building and using a patch, but it was just the same. Can you tell what I should change to get the results I need? Thanks, Alina ... View more

It sure helps. Thanks 🙂 ... View more

It works. Thanks! ... View more

Thank you for the answer. I'm downloading a Premier evaluation right now. Is there a link to a tutorial with installing services with Premier that I can follow? ... View more