[Mono-list] Xheo License Management

Dan dan@astusa.com
Tue, 25 May 2004 11:36:50 -0400

This may be a dumb question, but why would Xheo have pInvoke issues when it
attemps to read an embedded resource license in the assembly?  I don't see
why pInvoke calls would be used in that instance.  Is their license
verification library unmanaged?  If so, perhaps they should convert to
managed and obfuscate the heck out of it.


-----Original Message-----
From: mono-list-admin@lists.ximian.com
[mailto:mono-list-admin@lists.ximian.com] On Behalf Of Ed Stewart
Sent: Monday, May 24, 2004 2:53 PM
To: mono-list@lists.ximian.com
Subject: [Mono-list] Xheo License Management

I'm trying to use an assembly that is licensed managed by Xheo. I've been
able to compile a simple test application with mcs, and I have a valid
temporary key in the local directory. However, when I try to run the test,
the license manager throws an exception because it cannot find a valid
license. I have also tried to embed the license in my executable using
-resource:runtime.lic as suggested on the Xheo website, but this didn't

Of course, running under Mono is totally unsupported, so I don't really have
anywhere to go for official help. For Windows, Xheo supports probing for a
license, but beyond the current directory, everything is OS-specific
(including the registry and a c:\Program Files location).

Does anyone have any experience with this?

Mono-list maillist  -  Mono-list@lists.ximian.com