Oleg Rakhmatulin

After analyzing all the pros and cons of this switch and required amount changes in the source code I've decided to postpone such critical change till next major release.

We have too many features in our deserialization code which heavily depends on JSON.NET library features and now I don't see any real reason for rewriting all this stuff using...

We need this one for issue #144 (at least for the REST part of this issue).

Another good reason to postpone it till .NET 6 release: [no-reflection solution](https://devblogs.microsoft.com/dotnet/try-the-new-system-text-json-source-generator/) via source generators!

The main roadblock for proper trimming support is a Newtonsoft.Json package. We should return to this issue after implementing the epic #145 feature.

@dukeajuke If you have problems with building `UsageExamples` project from sources - just open a separate issue and attach the build output with errors. I'll try to help you to...

@dukeajuke I've never heard about any limitations on simultaneous connections on Alpaca REST API. Most probably you'll not be allowed to open several web socket connections to Alpaca or Polygon...

@ooples Unfortunately, I'm unable to provide you full access to Wiki but you can create a new .MD file in the root folder of this repo, write a tutorial, and...

@natehitze Alpaca re-designed their documentation site completely. Right now it provides only reference information without any code snippets or tutorials. Of course, the old version can be restored from Git...

It's not an error in SDK. The server returns the HTTP 500 status and HTML body. The SDK tries to parse response content but has no success - the resulting...