On May 11, 11:10 am, SugarDaddy <eric.ols... RemoveThis @gmail.com> wrote:
> On May 10, 9:43 pm, "Ronnie Vernon MVP" <r... RemoveThis @invalid.org> wrote:
>
> > SugarDaddy
>
> > Microsoft has a free forum, staffed by Microsoft developers who answer these
> > questions everyday. You can access them here:
>
> > MSDN Forums:http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=24&SiteID=1
>
> Thanks for the response. Unfortunately, this question was already
> asked in the MSDN forums and has no answer:http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1542029&SiteID=1
>
> The <assemblyIdentity> element in the uac.manifest seems to have no
> effect on signed or unsigned assemblies.
Thanks to Matt on MSDN forums for this solution:
Simply specify the /d switch on signtool to specify the application
name. (I could have sworn I scoured the signtool documentation for
something like this... oh well). So the command in the post-build
step might look something like this:
"$(DevEnvDir)..\Tools\Bin\signtool.exe" sign /n "Name of My
Authenticode Cert in the Store" /t
http://timestamp.verisign.com/scripts/timestamp.dll
/d "My Application Name" "$(TargetPath)"