Replies: 2 comments 2 replies
-
I don't think I would ever go back to .NET Framework; I just have too much bad experience with it and see very little benefit. First of all, that .NET Framework is always available on Windows is basically a lie. So many times I have to go through the frustration of helping customers troubleshooting corrupted .NET Framework, wrongly reported version, or other stuffs along that line. With bundled .NET Core, I have no complaint so far, and I really appreciate that consistency. .NET Framework is also dead, so I don't expect any issues to get fixed nor any new features. I believe DevExpress will move eventually. Please understand that I am in no way not appreciate your contribution; I just can't go back to .NET Framework myself. |
Beta Was this translation helpful? Give feedback.
-
I think your observations are correct. I had been writing Windows Forms applications for nearly a decade, having only stepped away from it in the past two, happily moving on to backend service work. Only after you bring it up do I remember all the troubles we had dealing with various frameworks on our client's machines. I think the solution is for me to learn more about how to do Windows application development using WPF and .NET Core. Thank you! |
Beta Was this translation helpful? Give feedback.
-
First off, great app. I really appreciate the work you've put into this.
I pulled latest with a thought of contributing a map integration but I'm having trouble due to the UI targeting .NET 5. Considering this is for Windows only, and is a GUI, had you considered using .NET Framework instead of .NET 5? There are many more controls available for .NET Framework. The only map control I could find for .NET 5 are from DevExpress and similar vendors.
Beta Was this translation helpful? Give feedback.
All reactions