It writes to the registry?
My Code Protected bits are failing with the following error when I run my application under limited user account privileges:
>>> 9/12/2007 6:08:12 PM: Error, [SOLIDCast.exe:656,User:Limited] - Exception GenException: Failed to set registry parameter [_tmpbalikeda63] to value System.Byte[]
The application then crashes with an 80131600 Automation error, since the exception can't be handled through COM Interop.
The module I apply code protection to runs perfectly without the code protection under a limited user account, and the portions which aren't protected likewise run just fine. But my application *must* run under limited user privileges. I can't have any Vista UAC boxes popping up.
Which portion of the registry is the Code Protector trying to write to, and why? Can I make it stop doing that?
OK, I found the registry entry, at HKLM\SOFTWARE\SecureLM. And I can specify access rights during install to that area for the machine's Users group and succeed at getting a Limited User to run it all.
One of the things it's doing is depositing the log file in my application's Program Files area, which I know won't pass muster with Vista. I suppose virtualization might hide that detail, but I'd rather not have to depend on it.
Is there a way to specify a different location for the log file, such as the [CommonAppDataFolder]? I can set the HKLM\SOFTWARE\SecureLM\Log key's "LogFileDirectory" value at install time to something more palatable. If I do so, will the SecureLM system honor that setting?
Terrence,
I've seen the material at softwarepotential.com. There is less information there than I was able to get in a two hour conversation with Yigal. Far too much "coming soon" and "real soon", far too little actual meaty stuff. I can't sell vaporware or betaware to a customer or to my boss.
Further, blogs (and c9 videos!) are nice for what they're worth, but they're far too disorganized to impart fundamentals which a demo and a reference guide simply can't deliver.
I'll certainly take an interest in the newer platform if the code protector fully supports generics and virtual calls.
Rob
Hi Rob,
It's hard to replace real-time conversation about specifics with marketing material. ;>) -- However, on October 1st we will be launching the new product and with it, some very good code samples and 'how to's' -- Hope you'll drop by and give it another look.
Terrence Nevins
Program Manager