I am explaining how to use the Bouncy Castle open-source library and how to implement ECIES.

Overall, .NET will run on most systems (x86, x68 and ARM), and there are many open-source projects which use C#. The Bouncy Castle library…

I am explaining how to use the Bouncy Castle open-source library and how to implement ECIES. My main focus is on outlining these. I could present in Java, but my preference is for C#. Most Java coders, though, will be able to easly move from C# to Java for the Bouncy Castle library.

Overall, .NET will run on most systems (x86, x68 and ARM), and there are many open-source projects which use C#. The Bouncy Castle library is a good example of an open-source library and is supported in both C# and Java.

Generally, .NET is a good fit for encryption and privacy, as the .NET framework is generally more robust than most other languages. Also, if someone has a Microsoft architecture, .NET Core provides one of the best integrations around and supports most things in a common platform.

For being tedious, I am not forcing anyone to read it. Overall, I am explaining the core principles of the methods and not the details of the code. Most developers will understand how to read C# code and then convert it into another language. My main aim is to show the method working and get a test run that provides insights into how the method actually works. In cryptography, we often implement it in many different languages and on many platforms, and we need to understand how to convert from one language to another.

On my Web site, I implement most of the programming languages around and will generally try to explain the methods rather than focus on specific implementations of a certain programming language or environment.

And finally, .NET is open-source and cross-platform. It is generally faster, more portable (and has an executable form), more robust and has better security than Python. It is fully backwards compatible, and which cannot be said for Python. C# has a better syntax and structure than Python, too.