I'm using InstallShield's Signing feature to digitally sign all my EXEs and DLLs in my InstallScript MSI project. Because we include a couple of third-party DLLs and SQL drivers, I added some exceptions to the "exclude patterns and files" list.
Unfortunately, InstallShield ignores those exceptions and signs those file anyway.
Is there something I'm doing wrong or is this a bug I've encountered?
I've not seen this behavior; could you provide more detail as to exactly what relevant entries you have in the include and exclude lists, and what excluded files are getting signed?
x - Sign Windows Installer Package 0 - Sign setup.exe x - Sign files in package
Include patterns and files: *.dll *.exe
Exclude patterns and files: chartdir30.dll SQLSRV32.dll sqlncli.dll
0 - Sign files that are already signed
--------------------------------------
chartdir30.dll and SQLSRV32.dll end up getting signed despite being in the exclude list. sqlncli.dll doesn't get signed because it is already signed by Microsoft.
That sounds like it should work by doing what you expect. Can you verify two things for me? First, are your source versions of chartdir30.dll and SQLSRV32.dll already signed with your certificate (perhaps due to some testing mishap earlier)? Second, do it work right if you remove those excludes and select them in the Exclude Files browse dialog? This will make sure it's using the exact name and install path; while the full install path shouldn't be required for this, it can't hurt to try it.
I double-checked and the files are NOT previously signed.
When I tried to use the Browse button to select the files, I got an access violation error. Now that I think of it, that is why I manually added each entry in the first place.
I tried typing adding the fully qualified path to the excluded file names but it still signed the files.
Note that the full path would be something like [INSTALLDIR]Subdir\Filename.exe. As for why there's an access violation, do you get similar results from visiting the files and folders view, or anything like that? Often that's related to invalid entries in the Directory table, and maybe that's somehow blocking the name resolution. Running MSI validation may point to something useful, or if you can send your ism file (no supporting files should be necessary) I can look into it: murman@macrovision.com.
Looks like adding the appropriate path qualifier (ie [INSTALLDIR], [SystemFolder]) fixed the problem. Thanks a lot.
I didn't enounter any errors with the File and Folders view or anywhere else that might explain the access violation issue. I'll send you my .ISM file in hopes that it you can help you track down the access violation issue.
