That's more to do with UWP being a AOT platform than it being deprecated; it should still work fine with .NET Core?
4,573 karma · joined September 7, 2015
That's more to do with UWP being a AOT platform than it being deprecated; it should still work fine with .NET Core?
Object based collections are generally deprecated over the generic versions and were existed prior to generics being introduced.
They are also bringing WinForms and WPF forward to work on .NET Core 3.0; and its still supported https://blogs.msdn.microsoft.com/dotnet/2018/10/04/update-on...
Code Access Security and Security Transparency aren't supported on .NET Framework either
Doesn't look that way
Top 50 Products By Total Number Of "Distinct" Vulnerabilities https://www.cvedetails.com/top-50-products.php
Vulns Product
1. 2124 Linux Kernel Linux OS2. 2084 Mac Os X Apple OS
3. 1924 Android Google OS
4. 1741 Firefox Mozilla App
5. 1664 Debian Linux Debian OS
6. 1546 Chrome Google App
7. 1495 Iphone Os Apple OS
8. 1123 Ubuntu Linux Canonical OS
9. 1103 Windows Server 2008 Microsoft OS
10. 1057 Flash Player Adobe App
11. 984 Safari Apple App
12. 961 Windows 7 Microsoft OS
13. 951 Internet Explorer Microsoft App
14. 951 Acrobat Adobe App
15. 856 Thunderbird Mozilla App
16. 818 Windows Vista Microsoft OS
17. 784 Opensuse Novell OS
18. 731 Windows Server 2012 Microsoft OS
19. 731 Windows Xp Microsoft OS
20. 698 Seamonkey Mozilla App
21. 685 Acrobat Reader Adobe App
22. 665 Windows 8.1 Microsoft OS
23. 641 Mac Os X Server Apple OS
24. 636 Windows 10 Microsoft OS
The startup and identity/authentication is a bit different though.
If you are using Blazor as a full desktop app (e.g. Electron) then you can use .NET Core on the client and that can talk to the javascript as a local server; but for running in the browser directly as WebAssembly it uses the Mono (WebAssembly) runtime.
XboxOne can run UWP and for that you can use .NET Core (via UWP) in a "shared" mode; however it also has a dedicated "game OS" mode (which most boxed/AAA games use) which takes priority over everything and has full hardware access, but that doesn't allow Jitting so you can't use .NET Core in that mode.
Mono and Unity have mature AoT compilers so can run in this mode (Xamarin also need AoT for iOS and Android which also don't allow Jitting, and Unity needs it for a lot of the platforms they support. Mono and Unity use different approaches to AoT though)
Mono is now sharing C# source code with .NET Core (and it goes both ways); but as far as I'm aware .NET Core doesn't seem to be rushing to fill any of the gaps that Mono serves well (iOS, Android, etc)
Though they are working on an AoT version of .NET Core for Windows/Linux/macOS https://github.com/dotnet/corert but that seems to be more focused on competing with golang and rust's AoT single exe offerings.
For desktop UIs; we'll have to see what's next :)
7+ million requests per second on linux for a single server (maxing out a 10GBps network) isn't to shabby ;)
Also they run continuous benchmarks for all platforms in a wider range of tests https://github.com/aspnet/Benchmarks
With the results being public at https://aka.ms/aspnet/benchmarks
For client on Windows, UWP is .NET Core, and WinForms or WPF currently .NET Framework. Though .NET Core 3.0 is meant to bring the full set of Windows UI stacks to .NET Core https://blogs.msdn.microsoft.com/dotnet/2018/08/08/are-your-...
For Tizen you'd also use .NET Core
For client on macOS or Linux you use Mono
For games you'd probably use Unity (Mono based)
For iOS, tvOS, watchOS, Solaris, Android, Solaris, IBM AIX and i, BSD (FreeBSD, OpenBSD, NetBSD), PlayStation 4, XboxOne, WebAssembly you'd use Mono
Can still use Mono for client on Windows and the ASP.NET Core stack is quite happy running on Mono on the server; but they have different focuses.
If you were building a library you'd target the .NET Standard 2.0 "contract" and it would cover all the runtimes.
Then .NET Framework, .NET Core, Mono, Unity, etc runtimes then implement that contract so a library built against .Net Standard will work on any of the runtimes.
You can also build your reverse proxy using Kestrel.
Though IIS is more battle tested so they may be using that as front line server for such a high profile service as Bing
Then it uses SpanHelpers.SequenceEqual for byte which is vectorized
https://github.com/dotnet/coreclr/blob/04d9b557ef8b7c60a1194...
Looks like some file IO functions and __rdtsc
There are probably > 208 lottery winners in the same period; no one would suggest that as a lucrative approach to life.
> Frontier also calculated how contestants can best extend their stays: being part of the “original crew” increases your chances of staying for the duration over those who join the cast later.
Also being on 44 episodes of one of the country's most popular TV shows; you'd hope would bring some measure of success...
Repayment starts at £21,000pa; so if you earn £30,000 you'd pay back £37 per month
https://github.com/dotnet/corefx/blob/master/Documentation/c...
> We generally don't accept change proposals that are in bucket #1.
...
> Bucket 1: Public Contract Clear violation of public contract.
> Examples:
> - Renaming or removing of a public type, member, or parameter
> - Changing the value of a public constant or enum member
> - Sealing a type that wasn't sealed
> - Making a virtual member abstract
> - Adding an interface to the set of base types of an interface
> - Removing a type or interface from the set of base types
> - Changing the return type of a member
> - ...or any other incompatible change to the shape of an API
HDMI 2.0 for 4K is 14.4 Gbit/s
HDMI 2.1 for 8K is 42.7 Gbit/s