4 ms·

I gave up on chasing every new shiny thing MS produces. Winforms work great. They are stable - there are a million packages for it out there and it can work w

I gave up on chasing every new shiny thing MS produces. Winforms work great. They are stable - there are a million packages for it out there and it can work with the version of the framework that's installed with every copy of Windows.

teddyuk 7y ago
I have seen systems developed over decades and they are a complete mess, the worst had these components: - vb com+ - c++ dcom - c++ mfc - .net 1.1 winform - .net 4 - wpf - delphi Microsoft causes this by events like build which go “we are betting everything on x” then the year later it is “x was cool but look at xx” Gahhhhhh
- starik36 7y ago
  VB6 forms designer was actually really good. I don't there is still anything that rivals it in terms of stability, customization, speed and round-tripping.
kevingadd 7y ago
And it's open-source now! I'm looking forward to people creating a better, more portable winforms even if we can't get it from Microsoft.
- maxxxxx 7y ago
  Doesn't Mono have Winforms already?
  - kevingadd 7y ago
    Yes, but I don't personally know how complete it is. The only company using it that I'm aware of is Plastic SCM.
    - MordodeMaru 7y ago
      This is how we use it: https://www.mono-project.com/news/2019/02/13/plastic-scm-a-full-version-control-stack-built-with-mono/ https://www.mono-project.com/news/2019/02/13/plastic-scm-a-f...
mycall 7y ago
Too bad Winforms is butt ugly.
- tonyedgecombe 7y ago
  It looks native, it's fine. The problem I've found is high-dpi support is still a dogs dinner.
  - naikrovek 7y ago
    Pretty sure they've fixed that in recent releases (within 18 months, I believe) of Windows 10. You should only need to recompile to gain hi-DPI awareness, if I recall properly.
    - tonyedgecombe 7y ago
      No, there are still problems. My understanding is there will be further work on the .Net Core version although I haven't paid any attention to that so far.

teddyuk 7y ago

I have seen systems developed over decades and they are a complete mess, the worst had these components: - vb com+ - c++ dcom - c++ mfc - .net 1.1 winform - .net 4 - wpf - delphi Microsoft causes this by events like build which go “we are betting everything on x” then the year later it is “x was cool but look at xx” Gahhhhhh

starik36 7y ago
VB6 forms designer was actually really good. I don't there is still anything that rivals it in terms of stability, customization, speed and round-tripping.

kevingadd 7y ago

And it's open-source now! I'm looking forward to people creating a better, more portable winforms even if we can't get it from Microsoft.

maxxxxx 7y ago
Doesn't Mono have Winforms already?
- kevingadd 7y ago
  Yes, but I don't personally know how complete it is. The only company using it that I'm aware of is Plastic SCM.
  - MordodeMaru 7y ago
    This is how we use it: https://www.mono-project.com/news/2019/02/13/plastic-scm-a-full-version-control-stack-built-with-mono/ https://www.mono-project.com/news/2019/02/13/plastic-scm-a-f...

mycall 7y ago

Too bad Winforms is butt ugly.

tonyedgecombe 7y ago
It looks native, it's fine. The problem I've found is high-dpi support is still a dogs dinner.
- naikrovek 7y ago
  Pretty sure they've fixed that in recent releases (within 18 months, I believe) of Windows 10. You should only need to recompile to gain hi-DPI awareness, if I recall properly.
  - tonyedgecombe 7y ago
    No, there are still problems. My understanding is there will be further work on the .Net Core version although I haven't paid any attention to that so far.