Hi All
About a year ago I asked this question:
Our PB12.5 project build was set up to use an External Manifest because we have a web service component we use to consume a web service. With the new PB2017 we wish to use the PBC170.EXE utility on a stand-alone build PC. However, how do we configure PBC170.EXE to recognize the Project Security External manifest option?
The reply I received at the time from Appeon Support:
The Project Security External manifest option is not support, we will record it as a requirement in our CR pool, I will get back to you once we have a plan to support this feature.
I have recently moved over to Appeon 2017 R2 Build 1769.
I note that when I set the project painter Security setting to: "No manifest" the PBC170 syntax reads:
/d "C:\DEV\myapp.pbt" /o "C:\DEV\myapp.exe" /w n /f /m n /x 64 /bg y /p "My App" /cp "My Co" /de "My App" /cr "LCP 2016" /v "17.0.0.1666" /fv "17.0.0.1666" /ge 0
But if I change the Security setting to: "External manifest - As Invoker" the PBC170 syntax now reads:
/d "C:\DEV\myapp.pbt" /o "C:DEV\myapp.exe" /w n /f /m n /x 64 /bg y /p "My App" /cp "My Co" /de "My App" /cr "LCP 2016" /v "17.0.0.1666" /fv "17.0.0.1666" /ge 2 /le 0 /ps n
As can be seen there is a difference at the end ("/ge 0" vs "/ge 2 /le 0 /ps n"). Does this mean that my original question has been answered? I have not heard back from Appeon support as promised in their reply. I'm running tests to see if PBC170 now supports external manifests but it would be nice to get explicit confirmation rather than assume this as an "undocumented feature".
TIA
Larry Peters
FYI ... PB 2017 R3 (due out later this month) will also add these features to the PBC as well ..
ProductVersionNum. Corresponding runtime parameter: /vn
FileVersionNum. Corresponding runtime parameter: /fvn
HTH
Regards ... Chris