Looking to deploy a component we have just purchased, and struggling with license exceptions
The control is from Atalasoft (www.atalasoft.com). I have the licensed sdk on my machine, and the assembly works great. However, looking at their deployment instructions (which are all geared towards VS/C#), they expect a licx file to be generated and delivered with the executable - details here http://www.atalasoft.com/KB/article.aspx?id=10128
I am trying to create the licx file manually and then compile into a binary using a tool which comes with Visual Studio, LC. Details on this kb entry http://msdn.microsoft.com/en-us/library/ha0k3c9f%28v=VS.100%29.aspx
Has anyone done something similar in that past? Is this a standard way .NET components are licensed and it supported by Openedge?
Thanks!
You may find this article in the Progress K-Base interesting.
Thanks Mike.
What a pain! Followed the instructions to the letter, generated the required OELicense.dll and placed in the $DLC/bin, but still get the license exception.
I've built the OELicense.dll on my machine and deployed to the target deployment machine, assume this is correct?
Thanks.
Atalasoft are saying that the license details need to be embeded in a executable and not an external dll.
Assume that is not possible with prowin32.exe ?
No that’s not possible. But I’d open a tech-support case for this with PSC..
Atalasoft are saying that the license details need to be embeded in a executable and not an external dll.
Assume that is not possible with prowin32.exe ?
Flag this post as spam/abuse.
This kb entry from Atalasoft details how they expect a executable to be built.
www.atalasoft.com/.../article.aspx
They specifically state the requirement to build the license file into the exe and not any other dll.
Will log a case with TS in the morning when I am back in the office.
Thanks.