The page for 2008 R2 Express is http://www.microsoft.com/downloads/details.aspx?familyid=8b3695d9-415e-41f0-a079-25ab0412424b&displaylang=en&Hash=Zyv%2fIlY0jMJ39QCjdf%2b0z8TewjrbmHFfVWpLFAve3vYc5BYxrjzxoa2JJRvFLWUQVoY%2f%2bqRDGstaHsYzCeQn9w%3d%3d#filelist You may want to dig into the html source code to find the real url from the hyperlink. Take SQLEXPR_x86_ENU.exe for example you will find the following link in the code: http%3a%2f%2fdownload.microsoft.com%2fdownload%2f5%2f1%2fA%2f51A153F6-6B08-4F94-A7B2-BA1AD482BC75%2fSQLEXPR_x86_ENU.exe So its real url should be: http://download.microsoft.com/download/5/1/A/51A153F6-6B08-4F94-A7B2-BA1AD482BC75/SQLEXPR_x86_ENU.exe Seems a little clumsy though, not sure if anyone else has any better idea. 😄 Sometimes the browser will parse the link and display in the address bar, unfortunately it's not the case here. ... View more

Replace ProgramData with your Y. ... View more

The File Version is the version of the setup.exe wrapper and I don't think you can specify its value in IS, however you can use utility like StampVer.exe to get this done easily. ... View more

There is a related post: http://blogs.msdn.com/astebner/archive/2004/08/24/219764.aspx ... View more

Is the file1 exactly the same between your old version and new version? ... View more

Maybe this blog can give you a start point: http://blogs.msdn.com/patricka/archive/2008/03/05/detecting-what-server-roles-are-installed-on-windows-server-2008.aspx ... View more

A simple vbs example: Function Get7zDir() On Error Resume Next Dim objReg Set objReg = CreateObject("WScript.Shell") Get7zDir = objReg.RegRead ("HKCU\Software\7-Zip\Path\InstallDir") End Function However, are you sure you're looking for the right key/entry? "Path" is an entry and has value like "C:\Program Files\7-Zip". So I would use Get7zDir = objReg.RegRead ("HKCU\Software\7-Zip\Path") BTW: you can also use the AppSearch and RegLocator tables to read value from registry. ... View more

Double check if the shortcut keyname has been correctly included in the RemoveFile table. Or doing a msi validation would likely to give you some clues. ... View more

Here is some info about the project types: http://documentation.installshield.com/robo/projects/installshield16helplib/ProjectTypes_Determine.htm One of the points kind of relates to your question: •You want to maximize compatibility with administrative tools such as SMS, or if your software will be customized by corporate system administrators prior to deployment. The Basic MSI project type gives them the flexibility to create transforms for the installation package and its associated properties, without repackaging your installation. ... View more

Glad it helped. I assume you already fixed it by changing the ".NET Scan at Build" option to Properties Only or None. Actually I set the default .NET scan at build component setting to Property Only in Tools->Options->.NET. Well, this may not apply to everyone though, as missing dependency will cause app fails to run. ... View more

Try to disable UAC to see how it goes? ... View more

So every registry piece is there after you execute the app with /regserver? We used to add the SA build engine to the exception of DEP to solve the problem with the precondition that all the dependendies for the app are present. Since you disabled DEP already so that should not be a problem. Maybe you want to use Dependency Walker to load your app just to make sure that all the dependencies are there. ... View more

Specifying the Previous Package in your release flag will help you to solve potential problems caused by dynamic linking. Dynamic linking for major upgrade is usually fine. One typical problem for using dynamic linking in minor upgrade (patch) is that files/folders might be removed in the minor upgrade but InstallShield will build the package without error due to the nature of dynamic linking. We know that we cannot remove component during minor upgrade, which would cause the corresponding feature to be converted to Advertised state. An advertised feature will cause the files fail to update and future patch/repair fails as well. ... View more

I think you can just open the msi directly in InstallShield, and then compare the components association with your ism project (hopefully you have isolated that by installing which feature will bring you the unexpected component, go for that feature directly). To my guess, it would have one more component associated with that feature comparing to your ism project. By saying so, I'm assuming that you have componet set as Scan .NET Dependencies and Properties, which would add missing dependency (could be from component or merge module) automatically for the components during building the msi package. Not sure if this fits into your case, however I met similar problem with this cause. ... View more

Cannot reproduce your issue with IS2009 Pro though. My guess is that somehow the binary data which save the icon file gets removed as well when you delete the button control. I sort of cannot convince myself as the icons are different for "Up One Level" and "Create New Folder". Anyway, please go to Control table to find about what the binary name used for the NewFolder button of InstallChangeFolder dialog (The default name is NewBinary2), and then go to the binary table to verify if the binary actually exists still or not. ... View more