Following this link, LockPermissions Table http://msdn.microsoft.com/en-us/library/aa369774(VS.85).aspx, "BUILTIN" wont work as the field must be formatted. Peter. ... View more

Are you building your project files with IsCmdBld.exe? If so you can set a different product name using the -z parameter. As for dialog backgrounds a solution is to have the same name for different graphics, located in different folders and use the -l parameter to specify the right path variable. For more info you can search Help for "Using ISCmdBld.exe to Build a Release from the Command Line". Peter ... View more

Look up in your help file "Specifying the Product Version". In the Version setting, enter the complete version number for this product. The version number must contain only numbers, and it must be in the format aaa.bbb.ccccc, where aaa represents the major version number, bbb represents the minor version number, and ccccc represents the build number. The maximum value for the aaa and bbb portions is 255. The maximum value for ccccc is 65,535. You can include a fourth field, making the product version format aaa.bbb.ccccc.dddd, but Windows Installer does not use it. ... View more

What OSs are your machines running? ... View more

Use 'SID: S-1-1-0' instead of 'Everyone' http://support.microsoft.com/default.aspx/kb/243330 Peter ... View more

Read my post here: http://community.acresso.com/showpost.php?p=425091&postcount=4 Good luck, Peter ... View more

Following this link content leads you to the "redist.txt" file located in your Visual Studio installation directory. All redistributables listed are to be "distributed unmodified". Regards, Peter. ... View more

I am pretty sure that modifying the original redistributable package breaks the licence terms for Redistributable packages from MS. I would be very careful in implementing this for packages that you release. ... View more

When you perform an administrative install, the .msi file changes size, therefore, loses digital watermark. I would recommend building an uncompressed release and sign the .msi file. ... View more

Hi there. To start with, I wouldn't test software on development machines. Or develop software on test machines. To answer your question though, you can disable the Windows Installer service. This will apply to all installed products, not just yours. The advantage is that you don't have to change your Installer project at all. Peter ... View more

type MySetup.exe /? and see what you get. also you can open Setup.ini with notepad and try to see if any of that makes sense to you. best of luck! Peter. ... View more

You can set the component's attribute as not shared. As a best practice you should only set the "shared" bit when you install in common locations (as Program Files\Common Files, System32, etc). ... View more

You need to have different ProductCode properties in your packages. Use ISCmdBld.exe to build your releases and pass different ProductCode properties using -z parameter. ... View more

If your release has a Setup.exe, you can target the "MSI Engine Version". Otherwise if you only have a MSI you can use VerFindFileVersion function or VerGetFileVersion ... View more