Thanks :)

We intend to move the C++ layer (it's called `teos`) into a separate repository, with EOSFactory having it as a dependency. So yes, once we do that you could use `teos` as a foundation for other projects.

Actually, we'd love to see it being used that way, as it was designed with this purpose in mind - that's why it's a static library, not an executable like `cleos`.

However, there is one important thing we need to take into account: `teos` is dependent on EOSIO source code, which unfortunately is incompatible with Windows - you cannot build EOS with any C++ compiler that's available on Windows. We've tried it for a long time and it looks quite hopeless. The main obstacle is that EOS is heavily dependent on an integer type that's not supported by Windows.

So I guess any .NET-based solution is out of reach, at least at this moment.