Your having enough of crackers, reverse engineers ? With LiteCode you can host your code remotely at a server where no cracker can touch it
Your source code will become even more private then ever with more protection and no source code obfuscation required
The dummy class in the client is being used to inject code but that's not important
Code is being injected in the dummy class so that you're able to call method's at the server side
The code from the server side will never leave or being sent to the client side
The most important part here is that the server contains all the sensitive information and the client does not
2. When TestDelegate method is being called in client side the client is able to call the delegate which will go back to the server and call your private method
this way you can just call BeginInvoke methods which require a callback method or BeginSend/BeginReceive from the Socket class
Example code - Server Side:
Example code - Client Side:
output at server side:
Value from server side: some value...
Your source code will become even more private then ever with more protection and no source code obfuscation required
Features
- Using the SSP protocol for having a scalable server and having the traffic Encrypted/Compressed http://ssp.codeplex.com/
- Host your code where no cracker can ever touch it to get your software cracked
- You don't need a lot of knowledge about networking how to send packets and such thats all being done in the background
- Shared Classes is a new technique to remotely call methods in the client or server to make it easy for the end-user to understand what is going on in the code
- Shared Classes
- System classes (underconstruction) currently there is, Graphics, Cursor
- Delegates (callback methods), Example is below
- Supports Properties, overloaded methods
Underconstruction
- "out" keyword
- "param" keyword
Code example of a shared class - Server Sided
class TestClass : ITest { privatestring Password; public TestClass() { this.Password = "VerySecretPassword"; } [RemoteExecution] publicstring CallMe() { return"Hello World"; } }
Code example of a shared class - Client Sided (Dummy Class)
class TestClass : ITest { public TestClass() { } [RemoteExecution] publicstring CallMe() { return""; } }
The dummy class in the client is being used to inject code but that's not important
Code is being injected in the dummy class so that you're able to call method's at the server side
The code from the server side will never leave or being sent to the client side
The most important part here is that the server contains all the sensitive information and the client does not
Delegate example
1. You are at the server side and you call a method TestDelegate and you give your private method as delegate2. When TestDelegate method is being called in client side the client is able to call the delegate which will go back to the server and call your private method
this way you can just call BeginInvoke methods which require a callback method or BeginSend/BeginReceive from the Socket class
Example code - Server Side:
LiteServer server = new LiteServer(539); server.onClientConnect += (Client client) => { ITest test = client.GetSharedClass<ITest>("test", typeof(TestClass)); string ret = test.TestDelegate(":O", (string val) => { return"some value..."; }); Console.WriteLine(ret); }
Example code - Client Side:
[RemoteExecution] publicstring TestDelegate(string SomeValue, TestDel CallMe) { return"Value from server side: " + CallMe("some string from Client Side :)"); }
output at server side:
Value from server side: some value...