We are preparing a WPF XAML browser application for certification. We use Advaced Installer for creatnig a msi installation file.
We have no problem with signing correctly the msi file, but the app files (exe and dll) inside.
The strong names signing done by Visual Studio 2005 during publish is successful but SignTool verify says that the application is not signed though all parameters for signing are correct (the same as for standalone signtool). When we sign exe and dll files directly with the signtool after publishing from Visual Studio, they are verified as signed correctly but the application doesn’t start after installation, finding that the SHA1 hash of the app is different than this in the manifest file (as it was changed by the signing after publishing). And we have the vicious circle.
Any help or links to information would be greatly appreciated. Thanks