Ivan Shynkarenka

Results 148 comments of Ivan Shynkarenka

Yes trailing orders are supported. Trailing stop order - A trailing stop order is entered with a stop parameter that creates a moving or trailing activation price, hence the name....

Hello Charles! During creating a prototype of the fast matching engine I took many ideas from your repository and others. Of course I can put all necessary references and licensing....

You need C++ runtime to run this in release mode. Try to install VS redistributable packages: [Visual Studio 2015, 2017 and 2019 x86](https://aka.ms/vs/16/release/vc_redist.x86.exe) [Visual Studio 2015, 2017 and 2019 x64](https://aka.ms/vs/16/release/vc_redist.x64.exe)

You can also try new .NET Core version of server/client. It is written on pure C# without C++ dependency. It is recommended for .net projects - https://github.com/chronoxor/NetCoreServer

I believe your web project cannot load some C++ library. Make sure all this libs are available through PATH envar: ![image](https://user-images.githubusercontent.com/4397805/87840127-ac5b1c80-c8a6-11ea-8b48-ee112c20a68c.png)

Please check if VS 2019 redistributable packages are installed https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

Server side SSL code in `examples\SslChatServer\Program.cs`: ``` // Create and prepare a new SSL server context var context = new SslContext(SslMethod.TLSV12); context.SetPassword("qwerty"); context.UseCertificateChainFile("server.pem"); context.UsePrivateKeyFile("server.pem", SslFileFormat.PEM); context.UseTmpDHFile("dh4096.pem"); ``` Client side SSL...

You may also look into the new .NET Core implementations of the TCP/SSL servers & clients - https://github.com/chronoxor/NetCoreServer

You can annotate field as `[Hidden]`: ![image](https://user-images.githubusercontent.com/4397805/175918243-c3569744-9df1-4066-9642-fa9f2d5f3b5a.png) And its output will be `***`: ![image](https://user-images.githubusercontent.com/4397805/175918300-887c0c45-8838-4adc-9d35-a4abdfb3d998.png)

Ok, as I understand you want to have 'transparent' fields that are present in objects/clases, but not serializable/deserializable and not output in logger/std::streams. Am I right? When deserialzed this fields...