mesamune@lemmy.world to Technology@lemmy.worldEnglish · 3 months agoMicrosoft donates the Mono Project to the Wine teamwww.gamingonlinux.comexternal-linkmessage-square203fedilinkarrow-up1744arrow-down114cross-posted to: [email protected][email protected][email protected]linux[email protected]
arrow-up1730arrow-down1external-linkMicrosoft donates the Mono Project to the Wine teamwww.gamingonlinux.commesamune@lemmy.world to Technology@lemmy.worldEnglish · 3 months agomessage-square203fedilinkcross-posted to: [email protected][email protected][email protected]linux[email protected]
minus-squarechaospatterns@lemmy.worldlinkfedilinkEnglisharrow-up24·3 months ago.net core is the future but Mono is still important for running legacy .net framework applications like ones that use WinForms or WPF. That’s pretty much it. Anything new should go straight to .net core.
minus-squareMihieslinkfedilinkEnglisharrow-up8·3 months agoHm, WinForms and WPF with Wine you mean? Otherwise makes not much sense. Was WPF ever run in this combination!
minus-squarechaospatterns@lemmy.worldlinkfedilinkEnglisharrow-up3·3 months agoAh yeah. Mono didn’t support WPF, but Mono did support running WinForms apps natively on Linux without using Wine.
minus-squareMihieslinkfedilinkEnglisharrow-up2·3 months agoThe problem with WinForms is that at least serious 3rd party libraries do a lot of direct API calls I guess, hence Wine.
.net core is the future but Mono is still important for running legacy .net framework applications like ones that use WinForms or WPF. That’s pretty much it. Anything new should go straight to .net core.
Hm, WinForms and WPF with Wine you mean? Otherwise makes not much sense. Was WPF ever run in this combination!
Ah yeah. Mono didn’t support WPF, but Mono did support running WinForms apps natively on Linux without using Wine.
The problem with WinForms is that at least serious 3rd party libraries do a lot of direct API calls I guess, hence Wine.