TLSharp icon indicating copy to clipboard operation
TLSharp copied to clipboard

lack of support for .Net Standard and .net Core

Open barrywimlett opened this issue 5 years ago • 2 comments

This project compiles pretty much straight out the door for .netSTandard and .netCore 3.0

All that needs doing is to re-create the prjects files in the new format ( which is much nicer to read ), and then people can write telegram apps on android and ios/apple as well as windows desktop.

It will take longer to change the build pipeline to use a new build agent than it will to make the changes - there are at least two pull requests waiting for you with the required changes.

This is what you see when searching for TLSharp in nuget, there are SEVEN other packages ported to the new standard.

If you need help ask, you've done a great job and all anyone wants is to be able to use your code on new and exciting projects that aren't stuck in the net46x,47x cul-de-sac.

image

barrywimlett avatar Nov 26 '20 12:11 barrywimlett

Did you find a solution to avoid use of System.Reflection?

amirvenus avatar Jun 06 '21 02:06 amirvenus

Did you find a solution to avoid use of System.Reflection?

Why do we need to avoid relection? did you post in the wrong issue?

barrywimlett avatar Sep 07 '21 11:09 barrywimlett