I don't know how much help this is but...
Kernel-Mode Code Signing Policy (Windows Vista and Later) (Windows Driver Kit)
TESTSIGNING is for kernel code only. User code can, at this time, still operate without it. What you need to do --unless you are writing drivers-- is to include a manifest with some special settings to get around the UAC.
Manifest Files Reference (Windows)
In the example below you should only change the parts marked in red.
Code:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity type="win32"
name="AutoLogon"
version="1.0.0.0"
processorArchitecture="X86" />
<description>
Auto logon tool
</description>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*" />
</dependentAssembly>
</dependency>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker"
uiAccess="false" />
</requestedPrivileges>
</security>
</trustInfo>
</assembly>
The UAC will accept this manifest and allow user mode code to run uninhibited.
There is no programatic way around digital sigs on drivers that I know of. Most compilers will include a digtal signature into their resources as regbin resources, but there is very little support beyond that.
However; you can disable TESTSIGNING as described here...
The TESTSIGNING Boot Configuration Option (Windows Driver Kit)
But be aware this is system-global and may have unintended consequences with some software.