Anton

Same story for me. With 1.7 it was quite fast, with 1.8 it more than 30 seconds to load just 10 chats. Also same for the Connection events, using 1.7...

Using ``` TdLibBindingsExtensions.SetLogFilePath TdLibBindingsExtensions.SetLogVerbosityLevel ``` solved for me both issues

@ForNeVeR you now have access to the private repo. Please upgrade the packages to 1.8 and uncomment the code at MainWindow.xaml.cs line 178. Sorry for the code quality, this is...

@ForNeVeR also pushed the **tdlib_1_8** branch, you can take it. Just remove line line 46-47 at \TClient\TClient.cs to repro the issue. Thank you.

Small update: with SetLogFilePath and SetLogVerbosityLevel the TDLib working INCREDIBLE fast! Every single event, every call to TDLib function now happened almost instant. I'm impress from one hand and I...

and another update (sorry for spamming): SetLogVerbosityLevel is enough to make it work fast.

@ForNeVeR the async void is the normal practice for the event handlers in WPF. Actually, there is no choice there.

@Francisco-Gamino I thought it quite clear :) I want to use Exchange PowerShell module in Azure Functions. Exch cmdlets can be used only via remoting.

WPF is "a bit" different than UWP. GetStdHandle under WPF return null as pointer to STD_ERR.

OK, get it at the end, you must use ```options.MemberAccessStrategy.Register``` explicitly for all inner classes,