undefined | Better HN

0 pointspjmlp8y ago0 comments

R# also turns an useful PC into an airplane, increases the typing delay, does not offer UML modelling tools, database integration, database modelling tools, Windows Forms, WPF and UWP modelling tools, enterprise code navigation tooling, mixed mode debugging between native and managed code, code generation templates, GPGPU debugging, services and drivers debugging, profiling tools, task and threading debuggers with selective control with graphical visualization,...., what a Windows developer actually needs.

0 comments

2 comments · 1 top-level

scarface748y ago· 1 in thread

I’m assuming you mean Rider since R# is a part of VS. But Windows Forms? Microsoft basically abandoned that years ago. The writing is on the wall as far as the .Net framework, MS is showing no love for classic .Net. All of their energy is toward .Net Core. I jumped off of that train a year ago and don’t plan to look back. I’m a big fan of Core but classic .Net?

pjmlpOP8y ago

Yes, Forms. It is legacy, yet loved by many enterprise customers, lots of gigs available.

.NET Core will be relevant for our customers when it finally achieves 1:1 parity with .NET Framework features, until then not many will bother to rewrite their applications, they already have Java for non-Windows platforms with better libraries.

I had to port an application from .NET Framework to Java, because customer wanted it to run on Linux and .NET Core wasn't up to it, regarding the necessary features.

j / k navigate · click thread line to collapse