.NET Blog

This page[1] (which was linked elsewhere in the thread) provides the following info: > Since an expression needs to either have a value or throw an exception, a switch expression that reaches the end without a match will throw an exception. The compiler does a great job of warning you when this may be the case, but will not force you to end all switch expressions with a catch-all: you may know better! I haven't used the feature yet myself, so I can't say it definitively - but it sounds like it does provide compile time feedback while still allowing you to compile. [1]: https://blogs.msdn.microsoft.com/dotnet/2019/01/24/do-more-with-patter…

Does this mean .NET framework is being dropped slowly for new projects? Yes. It's not a secret. Microsoft has said that .Net Framework is basically in maintenance mode and "will move slower". They are moving EF6, Winforms, and WPF to .Net Core (Windows only). https://blogs.msdn.microsoft.com/dotnet/2018/10/04/update-on-net-core-… I've been developing on top of Microsoft environments for over 20 years and .Net is by far my favorite language. But, the writing is on the wall. Anyone who wants a long term career in development needs to run away from Windows as fast as possible and slowly move away from focusing exclusively on .Net. Linux even dominates on Azure. https://www.zdnet.com/article/linux-now-dominates-azure/ Microsoft knows that Windows can't compete in the cloud and selling Windows for desktops is not the future.

> "It out performs Microsoft’s generic SortedDictionary<TKey, TValue> (which is actually a red-black tree) by a factor of 2 for inserts and a factor of 4 for searches." I may have missed it, but I'd love to know the versions of .net framework this was performed against. I saw a really interesting post in MSDN about how they've been working on performance improvements for underlying data structures. I would love to see this up against dotnet core 2.1 or >. For reference, this was the post: https://blogs.msdn.microsoft.com/dotnet/2018/04/18/performance-improve…

From a MS blog post that was on the front page today[0]: > .NET Core is optimized for building highly scalable web applications, running on Windows, macOS or Linux. If you’re building Windows desktop applications, then the .NET Framework is the best choice for you. Nope, it's still the same MS as always. [0]: https://blogs.msdn.microsoft.com/dotnet/2017/11/16/announcing-the-wind…

What's with this exaggerated blog post? 1. It was announced in the open in June 2016 that .NET Core includes telemetry: https://blogs.msdn.microsoft.com/dotnet/2016/06/27/announcing-net-core… 2. If you use something you could at least follow changes between major releases, no? When did engineer stop being responsible people and read before using things? :-O

> Overall this is a great post! I just think that there is even more potential for perf with JITs than what the post implies. Specially if the JIT can reuse PGO from previous execution runs like MGO on .NET 4.5+ or Android 7. https://blogs.msdn.microsoft.com/dotnet/2012/03/20/improving-launch-pe… https://source.android.com/devices/tech/dalvik/jit-compiler

> I was under the impression that .NET is fully open source: https://dotnetfoundation.org/ That's not of much worth if the design process remains firmly in corporate hands. Microsoft is currently, slowly, opening the process to the community, but even then I expect corporate will continue driving most of the roadmap and keep veto on everything, very much like Swift — which is much much much further on that track than C# is, Microsoft having only created a C# design/evolutions mailing list and repository literally days ago, the ML was created on January 30th[0] and the repository was created and announced on February 1[1], the "community input" doesn't actually exit yet. [0] https://lists.dot.net/pipermail/csharplang/2017-January/thread.html [1] https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-language-st…

> If not what are the reasons for a startup to stay away from .NET CORE? I've been using .Net for over 10 years now, and just launched a new product on Asp.Net Web API + SQL Server + Orleans. Whatever Microsoft says, .Net Core is not at all ready. The tooling and libraries are still undergoing major (and breaking) changes. You'll spend more time debugging it than your own code. I (foolishly) tried to adopt it a year ago (RC), and again six months ago (1.0). Each time I ran into a critical bugs and omissions. .Net Core will probably, eventually be great. It isn't yet. Edit: Here's an example of the fun you'll have, published today: https://blogs.msdn.microsoft.com/dotnet/2017/01/30/announcing-net-core…

Assuming that by ".Net standard" you mean the traditional .NET Framework, the irony in this comment is awesome. .NET Standard is the newest of the new. https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-sta… The terminology is getting hard to follow :)

Agreed. Starting point PerfMon and PerfCounters, as an addition to great suggested profilers I would also have a look at PerfView / ETW. https://blogs.msdn.microsoft.com/dotnet/2012/10/09/improving-your-apps…

I'd recommend using the tutorials rather than just typing stuff and seeing what happens. The language and concepts are the same, but there are some big differences at the framework and platform level. The xUnit tutorial is here: https://www.microsoft.com/net/tutorials/csharp/getting-started/testing Those tutorials are pretty intro level, but they do cover some of the issues you ran into. Also, I'd recommend checking out the new Visual Studio 2017 RC with updated .NET Core tools and support for the csproj based projects: https://blogs.msdn.microsoft.com/dotnet/2016/12/12/updating-visual-stu…

> The new build system FOR .NET Core works great too with `dotnet build` They've deprecated it: https://blogs.msdn.microsoft.com/dotnet/2016/05/23/changes-to-project-…

Elm has great error messages which do this. F# is also adopting some of that style in F# 4.1: https://blogs.msdn.microsoft.com/dotnet/2016/07/25/a-peek-into-f-4-1/

Announcing .NET Core RC2 and .NET Core SDK Preview 1 https://blogs.msdn.microsoft.com/dotnet/2016/05/16/announcing-net-core… Announcing ASP.NET Core RC2 https://blogs.msdn.microsoft.com/webdev/2016/05/16/announcing-asp-net-… Announcing Updated Web Development Tools for ASP.NET Core RC2 https://blogs.msdn.microsoft.com/visualstudio/2016/05/16/announcing-up… ----- .NET Core RC2 is supported on the following platforms: Red Hat Enterprise Linux 7.2 Centos 7.1 Debian 8.2 (8.2, 8.3, 8.4)+ Ubuntu 14.04 (16.04 support is coming at RTM) OS X 10.11 Windows 7+ / Server 2012 R2+ Windows Nano Server TP5

> silverlight Hah, I forgot about Silverlight - mainly because I never used it (did anyone?) > razor/mvc Eh? Razor is very much still alive, and MVC lives on as ASP.NET Core MVC. > because in the real world, moving people from asp.net classic to .net core costs money. Yes, I live in the same world, and have migrated several projects from .NET to .NET Core. If you were an early adopter, it could admittedly be a bit painful, but everything "just works" now. > I mean, even .net standard came and went before we even started using it, considering it won't be part of .net core 3.0. Really not sure what you mean here, and I can only guess that you've been thrown by Microsoft randomly releasing new .NET Core versions before the corresponding .NET Standard versions - releasing the implementation before the API. I don't like this myself, but it hardly means that .NET Standard has "came and went". Also, just a couple of weeks ago, Microsoft said ".NET Core 3.0 as well as upcoming versions of Xamarin, Mono, and Unity will be updated to implement .NET Standard 2.1"[1]. [1] https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcing-net-stan…

More and better examples here https://blogs.msdn.microsoft.com/dotnet/2019/01/24/do-more-with-patter…

It's not. C#'s switch can pattern match on value and type: https://blogs.msdn.microsoft.com/dotnet/2019/01/24/do-more-with-patter… Java's switch still operates only on String, int, short, byte, char, and their wrapper types: https://blog.codefx.org/java/switch-expressions/

Here is an example of anomaly detection with ML.NET its not online learning based however. https://blogs.msdn.microsoft.com/dotnet/2018/11/08/announcing-ml-net-0…

Tensorflow models can be used in ML.NET and the API is open to suggestions for what to support next. https://blogs.msdn.microsoft.com/dotnet/2018/09/12/announcing-ml-net-0…

They've been releasing versions monthly, here are the last few release notes: v0.7 = https://blogs.msdn.microsoft.com/dotnet/2018/11/08/announcing-ml-net-0… v0.6 = https://blogs.msdn.microsoft.com/dotnet/2018/10/08/announcing-ml-net-0… v0.5 = https://blogs.msdn.microsoft.com/dotnet/2018/09/12/announcing-ml-net-0…

Yes, Bing runs on Asp.Net Core: https://blogs.msdn.microsoft.com/dotnet/2018/08/20/bing-com-runs-on-ne…

This doesn't look like "on life support" to me: https://blogs.msdn.microsoft.com/dotnet/2018/03/06/f-language-and-tool…

"The highlight of .NET Core 3 is support for Windows desktop applications, specifically Windows Forms, Windows Presentation Framework (WPF), and UWP XAML. You will be able to run new and existing Windows desktop applications on .NET Core and enjoy all the benefits that .NET Core has to offer." WPF, Windows Forms, and UWP are listed under the Windows-Only Desktop Packs section in the diagram. https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-supp…

https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-supp… Things are a bit more complicated than that, I guess that's specifically why Microsoft is open sourcing "the desktop pack", because it is not multi-platform.

WPF (and the other UI technologies listed) still rely on a lot of the underlying Windows API. Now that they are open sourced though, someone outside MS can work on a port, though I imagine it will take a non-trivial amount of effort. The change here is that .Net Core now supports it, but only if you reference the appropriate SDK[1] [1] https://blogs.msdn.microsoft.com/dotnet/2018/12/04/announcing-net-core…

This is coming in .NET Core 3. Slated for Q1 2019 AFAIK. https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-supp…

> Out of interest, what are the options for cross platform desktop apps, if the Windows GUIs are going to remain closed source? .NET Core 3 will support WPF -https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-supp…

Perhaps you're thinking of Microsoft moving Bing to ASP.NET Core 2.1, with a 34% performance improvement: https://blogs.msdn.microsoft.com/dotnet/2018/08/20/bing-com-runs-on-ne…

But they didn't, did they? Their performance optimizations have usually been at a lower level, fixing inefficient code and speeding hot paths, e.g.: https://blogs.msdn.microsoft.com/dotnet/2017/06/07/performance-improve…

Bing? https://blogs.msdn.microsoft.com/dotnet/2018/08/20/bing-com-runs-on-ne…