Tim,

[SB_6POOL] is a custom compiler variable and points to our server were all the files are located.

For example, [SB_6POOL] is set to \\Win7-64\corpdata in our case and resolved to \\Win7-64\corpdata\sb7.exe at compile time. We do this to have "portable" projects. You can also hardcode your path here, e.g. c:\test\sb7.exe or whetever.

Yes, in most cases, you can install on a WIN7 machine without code-signing your install (and application) files. But it is not recommended. Your customers will see an "Unknown Publisher" UAC popup.

And it's even possible that your installer can't be executed at all. An elevated application (e.g. installer) can't be started if the UAC-aware operating system (Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2) has the "User Account Control: Only elevate executables that are signed and validated" security policy enabled and the installer is not code-signed.

So in fact, a code-signing certificate is a must have today.

Does this help?

Friedrich