Hi,

Our controls are always packaged as a single DLL because the controls share a lot of common code. Some other vendors package different controls in different DLLs, that cause a lot of duplicate code to be rendered to the client side if you use more than one of their controls. On the contrary, we only render shared code once.

In any case, most users will not see what controls are in our DLL because they do not install our product on their machine. They will only get a single DLL that comes with your application. Some advanced user may be curious enough to dig into the DLL and see what's inside it, but that would be a violation of the license term.

When you purchase the suite, you will get a license file that unlocks all controls. If you need to, we can create a separate license file for you that will only unlock the controls you specified. That way your user will not be able to use any other controls even if they found out there are others in the DLL.

Please feel free to let us know if you have any more questions.

Thanks!

Great. Please feel free to let us know if you need us to make a separate license file for you.

That is correct. The remote user does not receive any DLL.




I think Tobias was talking about redistribute his application to his client. For example, A may use our product to develop an online shopping application and sells it to B. End user C will be accessing B'website. Here:

1. A would purchase a license from us and install our product in order to develop his application;
2. B do not need a license from us, nor he would need to install our product. However he will get a copy of our DLL, as part of the program A distributed to him, so that A's application would run on his server;
3. C does not need to get anything;

Hope this clears up.

Thanks