Better failure handling when signing a build fails

[shb]

When I try to build a signed application or installer, the build fails at the end of the build because of bad signature data. This is unpractical because it takes a lot of time for building all data and the entire build must be rerun anyway.

When building an executable, the data is deleted when signing fails. (This can be observed when watching the output directory.) The installer is left in place and seems to be working. Not sure which behavior is better. Please unify it.

Please check when closing the build assistant and early in the build process

• that the Personal store certificate exists
• that the Timestamp URL looks valid (at least is not empty)

When the build will not be deleted, maybe a hint could be shown how the code can be signed manually.

When the build will be deleted, please fail early in the build process (when the basic checks mentioned above do fail).

The attached project shows the currentbehavior. Abuildwill failbecausethereisnocertificatewiththisname. And after a valid certificate is selected thebuildwillfailbecausetheTimestampURLisinvalid.

Until now I did not succeed in signing a build because I do not know how the timestamp URL should look like. Therefore I already reported that the Timestamp URL should be better documented as a documentation suggestion (from the feedback link in the help). (No link to the suggestion because the feedback form is not a forum, sorry.)

[MohMah]

First of all you (NI) need to activate instantaneous commenting under your pages instead of asking a user in advance for filling hes/her personal details in your boring forms. Because immediate commenting is much more effective than the type you've decided on. Those who want to sent their opinion can be discouraged by the procedure you've devised and leave sending their comments.

Next is the non sense you've explained in your documents which comes below in quotes.

"LabVIEW does not generate events, such as Value Change, when you use shared variables, global variables, local variables, DataSocket, and so on."

You must activate 'Value Change' event generation when using above items especially when it comes to DataSocket. I see that the value changes in a remote computer but its corresponding event is not fired. By the way, the only method which remains is the funny way of immediate polling which wastes CPU time and severely occupies memory. The thing that you must have taken care of and you neet to take care of sooner or later.

[crossrulz]

MohMah, what does any of that have to do with this idea?  If you have an actual idea to make LabVIEW better, post in a new thread.  And this is not a board for complaining.  State it as an idea to make things better.