For desktop applications I'd say most of the improvements are more developer focused, but nevertheless it seems prudent to move forward to the currently recommended platform rather than holding out and hope things don't break or key libraries no longer support full framework (and there are more and more of those!). NET Framework code - while it still works - is slowly but surely falling behind in functionality and features compared to. NET Core isn't a major change in terms of product features, but it is one that I had to make at some point as. Related GitHub Repository for the Desktop Runtime Installer The Runtime Distribution is the focus of this post:ĭiscussion of Runtime Distribution modes for Desktop ApplicationsĬomparison of distribution modes and sizesĭescribe what I'm doing with Markdown Monster's Installerĭiscussion of a support tool that you can use to install the Desktop Runtime
No, what was holding me back was the issue on how to distribute the application without undue bloating of the download installer sizes or effectively getting the shared. For the most part it all just worked or could be fixed with relatively minor updates, although there were a few library dependencies that needed customizations or re-packaging for. NET Core was surprisingly painless even though MM has a boatload of oddball integrations. The technical aspects of the migration were never a big deal - the move from. NET Core over the last couple of years and recently got the final libraries moved over so that all existing features and built-in addins are now working on. However, I've gradually moved various parts that needed updates to. NET Core for some time I've kept it running on.
NET 7.0.Īlthough Markdown Monster has supported. I'm in the process of updating the next version of Markdown Monster to run under.
0 kommentar(er)
