MAGE不是Timestamping Manifest。 [英] MAGE not Timestamping Manifest.

问题描述

我们正在做什么的背景。

我们不希望每台开发者机器上都有我们的VeriSign证书，因此我们决定在TFS XAML期间进行所有代码签名构建过程。我创建了一个PowerShell脚本来完成此任务，除了为清单文件添加时间戳之外的所有内容。

脚本的大纲是：

删除.deploy扩展名 - >签署任何尚未签名的dll - >更新清单文件 - >重新添加.deploy扩展名。

在此过程之后运行clickonce会为我们提供有效的签名点击一次打包。

如果您推进系统如果日期超过证书的失效日期，则发布者信息将不再填充，您必须导航安全提示才能运行该应用程序。

以下是我运行的两个法师命令。运行这些命令时，所有项目文件都已正确签名并加上时间戳。

mage - 更新 $ file < span style ="color：＃a9a9a9; font-size：x-small">。 FullName
- CertFile $ certificatePath - 密码   ****** - TimestampUri 'http://timestamp.verisign.com/scripts/timstamp.dll'

mage - 更新 $ file 。 FullName
- CertFile $ certificatePath - 密码   ***** - TimestampUri 'http://timestamp.verisign.com/scripts/timstamp.dll' - appm $ fileManifestPath - 发布者 " MyPblisher" - SupportURL http://www.help.me - 名称 " MyProduct"

我的下一步是将所有内容移到Visual Studio项目中并尝试使用TFS / MSBuild发布项目并查看是否正确地为清单文件添加时间戳。

我使用的是此文件夹中找到的MAGE版本：

C：\Program Files（x86 ）\ MicroSoft SDKs\Windows\v8.0A\bin\NETFX 4.0工具

解决方案

您好jSlides，

>>我的下一步是将所有内容移到Visual Studio项目中并尝试使用TFS / MSBuild发布项目并查看是否正确地为清单文件添加时间戳。

我不确定您的问题是什么。您对clickonce有任何疑问吗？或者有关如何使用TFS / MSBuild发布项目的任何问题？

如果您可以与我们分享有关您的问题的更多信息，将会很有帮助。

最诚挚的问候，

Edward

Background on what we are doing.

We don't want our VeriSign certificate on every developers machine, so we decided to do all our code signing during the TFS XAML build process. I have created a PowerShell script to accomplish this that does everything but timestamp the manifest files.

The outline of the script is:

Remove .deploy extension --> sign any dlls that are not already signed --> update the manifest files --> add the .deploy extension back on.

Running the clickonce after this process gives us a valid signed click once package.

If you advance the system date past the expiry date of the certificate then the publisher information no longer populates and you have to navigate the security prompts to run the application.

Here are the two mage commands I run. When these commands are run all the project files have been properly signed and timestamped.

mage-update$file.FullName -CertFile$certificatePath-Password ******-TimestampUri'http://timestamp.verisign.com/scripts/timstamp.dll'

mage-update$file.FullName -CertFile$certificatePath-Password *****-TimestampUri'http://timestamp.verisign.com/scripts/timstamp.dll'-appm$fileManifestPath-Publisher"MyPblisher"-SupportURLhttp://www.help.me-Name"MyProduct"

My next step is to move everything into the Visual Studio project and attempt to use TFS/MSBuild to publish the project and see if that properly timestamps the manifest files.

I am using the version of MAGE found in this folder:
C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools

解决方案

Hi jSlides,

>> My next step is to move everything into the Visual Studio project and attempt to use TFS/MSBuild to publish the project and see if that properly timestamps the manifest files.

I am not sure what your issue is. Do you have any issues about clickonce or any issues about how to use TFS/MSBuild to publish the project?

It would be helpful if you could share us more information about your issues.

Best Regards,

Edward

这篇关于MAGE不是Timestamping Manifest。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！