http://blogs.msdn.com/b/shawnfa/archive/2008/01/24/manifested-controls-redux.aspxLast year, I made a series of posts about a new feature available in the betas of .NET 3.5 which enabled you to specify declaratively the set of permissions that IE hosted managed controls should run with. Since the betas there have been a couple of tweaksen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/shawnfa/archive/2008/01/24/manifested-controls-redux.aspx#9571086Mon, 27 Apr 2009 18:57:08 GMT91d46819-8472-40ad-a661-2c78acb4018c:9571086Pavel<p>It did not quite work for me. Here are some corrections to make this work:</p> <p>1. It is not ManifestControl.cer that has to be in Trusted Publishers certificate store. It is ManifestControl.cer's signing Certificate Authority that has to be there. </p> <p>Open .cer file, find the Certificate Authority certificate on the last tab (CA's name is Root Agency), copy it to a file and then install to Trusted Publishers.</p> <p>2. If you want to re-sign, it's not enough to call Mage.exe with /Sign parameter as stated in ManifestControl.html. After you update .manifest file its hash changes and you need to update it in .control file. Whole batch file will be</p> <p>mage.exe -Sign ManifestControl.dll.manifest -CertFile ManifestControl.pfx -Password password</p> <p>mage.exe -Update ManifestControl.control -AppManifest ManifestControl.dll.manifest -CertFile ManifestControl.pfx -Password password</p> <p>mage.exe -Sign ManifestControl.control -CertFile ManifestControl.pfx -Password password</p> <p>I hope it helps someone.</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9571086" width="1" height="1">