I have a C# project that uses a node-licensed 3rd-party control; I also wish
to deploy this using a signed ClickOnce manifest.
The 3rd-party license exists on my development box; the code-signing
certificate exists on the build server.
I don't really want to consume a license just for the build server, and I
shouldn't really have the [private-key section] code-signing certificate on
my desktop. Is it possible to convince MSBuild to create the manifest
without re-building the code itself (which will fail)? I guess I just want
it to use the existing binaries from the relevant bin folder.