It is definitely possible to upgrade from Installshield 7.0 to Installshield 2010. Why am I so sure? Because I did it recently 🙂 The install shield upgrade wizard did most of the conversion but there will obviously be a lot of tweeks and changes you will have to make to make it work perfectly after the upgrade. Good luck. ... View more

Prerequisites functionality works - you can either embed the entire prerequisite in your installer or use redistributable packages. Once the prerequisites are set, on installation, the installer checks/searches the target machine for these prerequisites and installs them only if they are not already present. you don't need search the target machine manually. The installer checks and installs all the prerequisites before starting your product installation. ... View more

The best way I can think of is using installscript. I don't think a basic MSI will allow custom components and installations based on the OS. ... View more

Thanks MichaelU, I took your advice and let UAC alone. Besides, I think every toggle of the UAC calls for a reboot so that entirely rules this option out. I cant have my installer rebooting twice. 🙂 I found a rather simple resolution/alternative to get rid of these errors. I moved the two files oleaut32.dll, stdole32.tlb to a component in another feature with the self register property set to false. This prevents the files to self ergister when Do(SELFREGISTRATIONPROCESS) is called. And I added this to my installscript to manually register these files. STRING szOleaut32, szStdole2, szTargetStdole2, szTargetOleaut32; szOleaut32 = "Oleaut32.dll"; szStdole2 = "Stdole2.tlb"; szTargetOleaut32 = WINSYSDIR ^ szOleaut32; szTargetStdole2 = WINSYSDIR ^ szStdole2; szRegsvr= "regsvr32.exe"; szCommandParms= " /s "; LaunchApp(szRegsvr, szCommandParms + szOleaut32 ); LaunchApp(szRegsvr, szCommandParms + szStdole2 ); This code will ensure that these files are registered. All I will to do is run this through a condition and register the files only if necessary for e.g. case the OS is not Vista or if better versions of the files are already present etc. In Windows Vista I know that there are better versions of these 2 files which are backward compatible. ... View more

First thing I did was to test this on a machine with non-dell hardware - The issue was replicated on other hardware so this eliminated the chance of it being a hardware issue. After a lot of effort I found that this error was caused because a system configuration file, 0x0409.ini was missing from my build. I included this file and error -5001: 0x80070002 didnt occur. I didnt find much information about 0x0409.ini configuration file on the internet. The issue is resolved but I am not entirely clear how or why this file caused this error. What is 0x0409.ini file? Any inputs are appriciated. Thanks ... View more

It looks like you are trying to recreate the prerequisite functionality of InstallShield. You can add custom setup prerequisites to your InstallShield package as redistributable or add them to the installer. Here is a good article about how to do it. http://shieldmaster.wordpress.com/2009/04/26/tutorial-adding-setup-prerequisites-to-installshield-package/ ... View more

InstallShield provides the prerequisites functionality. You can use this in your MSI project. This would ensure that these prerequisites are only installed if they are not already present in the target machine. If you do not want to include these components (SQL Server 2008, .NET Framework 3.5, WSE 3.0) into your installer then you can use the redistributable setup installer. For e.g. .net 3.5 redistributable setup installer is about 3MB and when this is included into the prerequisites of your InstallShiled project then the installer will check if .net 3.5 framework is already installed on the target machine and if not it will prompt the user and download the entire .net 3.5 framework and install it. I am not sure about Sql Server 2008 and WSE 3.0 but I am guessing they must have redistributable installers like .net 3.5 framework as well. ... View more

I recently upgraded from IS 7 to IS 2010. I didnt face any major issues as you did. The process of migration was simple. I was prompted if I want to upgrade my project. I selected yes. Then a prompt asking if I want to upgrade my installscript with the lastest notations (I don't remember the exact message but this is what it roughly meant.) I choose yes. The project migration was successful. But, I had a few compile errors caused by references of some obsolete header files etc. I removed these references and IS project worked fine. Now, I just have some bugs that I have to fix, but the IS project is compling and running fine. I guess similarly, it shoudl work with your IS migration from 6.x to 2010. Answers to your Qs (to the best of my Knowledge) 1. The migration backs up your project before it starts. Try re-doing it again. I am not sure but your error messages suggest it couldn't find some necessary file sections. Check if your existing project compiles nad runs fine. 2. Yes I am pretty sure this is the correct approach because I followed the same and it worked from me. 3. I dont think you need to create a new installshield project, migration should work fine. 4. If migration is successful then you nothing will be left out from the prev version. ... View more

Thanks MichaelU. Yeah, I need to distribute and register these files. Though, I haven't yet tested my application without registering these files during install hoping that the better versions of oleaut32.dll in Vista etc are backward compatible and wont cause problems to my application. Anyway a probable solution I can think of, though I am not sure if it will work, I need some help with this solution - 1. Toggle UAC in vista through InstallScript and then try registering these dlls. I remember seeing the permission level in Vista - Administrator doesn't have full control on the files like oleaut32.dll. Would this work? If its possible, how to enable or disable UAC through InstallScript? Thanks. ... View more