As windows security improves, more effort is made to alert users of "questionable" software. Such is the case with CVI executables which bear no digital signature and upon invocation bring up the "Open File - Security Warning". While users have the option to run or cancel, a digital signature is the right way to address the issue.
You mean you want to check the integrity of your EXE when you load it up?
Standard way is with a CRC checksum value. Store the value in a file and have your program calculate and compare the checksum.
Every time you recompile the EXE you simply recalculate a new checksum using another program (that uses the same CRC algorithm) and store it in the file.
If you want to use checksum stuff as Dave suggested to make your own certificate, you can check out the Cryptography functions which are the next item on the MSDN tree to the link I posted.
Great info! Were you asking about getting products
signed by Microsoft, or creating your own signature scheme? Looks
like that link was for win mobile users. I think this one is for regular Win32 users.