Charles Roddie
Charles Roddie
> I had to include refactors to merge the .NET Framework 2.0 projects with the .NET Standard 2.0 projects into multi-targeting SDK-style projects. @prepare I see that not all projects...
> I support .net framework 2.0 and netstandard2.0 projects That is crazy!
@prepare Can you do this officially? Unstable API is no problem. If not, do you object to anyone else publishing to nuget? In that case stating that it is both...
Is the stability of Typography improving? Could a nuget package be in sight?
Does Typography need to be forked to get a nuget package out?
netcore3 is not a good idea. netcore3 does not support Xamarin.iOS/Xamarin.Android/UWP. netstandard2.0 is the right target, and will be until dotnet5.
netstandard2.1 removes .net framework and uwp support so I would recommend netstandard 2.0 https://github.com/dotnet/standard/issues/1330
This should be reopened as there are still netframework2 projects in this repo! https://github.com/LayoutFarm/Typography/issues/191#issuecomment-658624831 .NET Framework 4.6.1 was introduced 5 years ago. What is the need to support older .net...
These users are still on XP? So they don't mind that they haven't updated their hardware for 11 years, haven't had OS feature updates for 12 years and security updates...
dotnet5 was scaled back so doens't support Android/iOS/UWP, with these plans pushed back to dotnet6. Regardless, a first step is to go netstandard2.0 only. > They are replacing the old...