Usability

By using .NET Enabled SmartCard, the programming difficulty of smart card level application can be reduced, and the developing cycle and cost can be decreased accordingly; these are benefited from the .NET Remoting technology undoubtedly. Now you could call the on-card class and function resided in the .NET Enabled SmartCard directly, from the .NET application in the customer PC, without thinking about the message structure of the APDU command and data, the transmission protocol for data sending to the Smart Card, and for response replying to the .NET application in the PC. Calling the on-card class and function in the most common and simplest way is all you needed during the real development.

Multiple Standard protocols are supported by.NET Remoting technology, such as XML, SOAP, and HTTP etc. Therefore, it is quite convenient for enterprisesto make .NET business deployments with .NET Enabled SmartCard running as a part of the solution. In addition, .NET Enabled SmartCard can also be served as a component of the distribution computation, so as to protect sensitive data and key code segment for security assurance.

With the built-in .NET CLR (Common Library Runtime) and .NET SmartCard Framework, .NET Enabled SmartCard supports not only C# but all programming languages to be used under .NET architecture in real development, such as C++/J#/VB.NET/JavaScript etc.; or you may even use the script language like Phthon to develop the smart card level application. To secure the return on business investment, the compatible-mode APDU commands creates a favorable communication method for the application to access the .NET Enabled SmartCard. Moreover, the user-defined APDU commands empower your existing application with good running status under any complex condition.