TLSharp/TLSharp.Core
Andres G. Aragoneses 77867b44e6 Use better exception handling
Parsing the message of an exception to decide what to do
next is a bad practice, because it's easy that the message
might be changed by mistake in the future. To enforce the
coupling in a stronger way it's better to use exceptions
of different type depending on the kind of error, so that
we rely on the compiler enforcing the behaviour when doing
changes in this error handling areas in the future.

This also makes the code a bit more simple and readable.
2016-10-22 22:00:15 +08:00
..
Auth Fix spelling of Receive 2016-07-20 08:15:28 +01:00
MTProto Update Everything 2016-09-22 17:01:59 +03:30
Network Use better exception handling 2016-10-22 22:00:15 +08:00
Properties TLSharp and Tests 2015-09-28 10:01:17 +08:00
Requests Redesign Everything 2016-09-24 17:08:26 +03:30
Utils formatting code (ctrl + k + d) 2016-04-18 15:20:57 +04:30
packages.config Redesign Everything 2016-09-24 17:08:26 +03:30
Session.cs - Layer 53 2016-10-15 13:35:54 +03:00
TelegramClient.cs Use better exception handling 2016-10-22 22:00:15 +08:00
TLSharp.Core.csproj Redesign Everything 2016-09-24 17:08:26 +03:30