Live data from Hacker News

Building and Running .NET’s CoreCLR on OS X

praeclarum.org

11–20 of 59 posts

Re: Building and Running .NET’s CoreCLR on OS X

#12
> Rewriting bits of high performance assembly in bytes (not opcodes) as Mac’s as refused to generate the desired instructions.

Ouch. They should really look into using clang and its integrated assembler. All mnemonics should Just Work. as on mac is a patched up binutils 1.38 version.

Re: Building and Running .NET’s CoreCLR on OS X

#15
Now as .Net becomes more interesting again (for me), can someone comment on the state of GUI app development in .Net?

Can I write cross-platform GUI code, or would I need to re-implement the GUI on every platform?

Do Windows .Net GUI apps (does that mean Windows.Forms?) work just as-is on Linux (and maybe MacOSX)?

What would be the best supported GUI .Net framework? QtSharp? Windows.Forms?

I found some overview here, but not sure if accurate / up-to-date: http://www.mono-project.com/docs/gui/

Re: Building and Running .NET’s CoreCLR on OS X

#16

Now as .Net becomes more interesting again (for me), can someone comment on the state of GUI app development in .Net? Can I write cross-platform GUI code, or would I need to re-implement the GUI on every platform? Do Windows .Net GUI apps (does that mean Windows.Forms?) work just as-is on Linux (and maybe MacOSX)? What would be the best supported GUI .Net framework? QtSharp? Windows.Forms? I found some overview here,…

WinForms works on Mono (but looks like ass). WPF doesn't. The best way is probably Gtk#.

Re: Building and Running .NET’s CoreCLR on OS X

#17
post #4

Earlier quoted context omitted.

> without crazy licensing fees as with Mono Are you confusing Mono for Xamarin?

No - Mono has crazy licensing restrictions and massive licensing costs for statically linking their framework. Xamarin offer a better option, but there is no "free" alternative using C#, nor could you create one with the Mono framework. The CoreCLR does have the possibility to get around this as the code required for creating a solution is not licensed in the same way. Xamarin's entire business model revolves around…

I think their business model revolves more around selling their proprietary bridges from Mono to mobile platforms' native APIs (MonoTouch and MonoDroid, now marketed as Xamarin.iOS and Xamarin.Android).

Re: Building and Running .NET’s CoreCLR on OS X

#18

Now as .Net becomes more interesting again (for me), can someone comment on the state of GUI app development in .Net? Can I write cross-platform GUI code, or would I need to re-implement the GUI on every platform? Do Windows .Net GUI apps (does that mean Windows.Forms?) work just as-is on Linux (and maybe MacOSX)? What would be the best supported GUI .Net framework? QtSharp? Windows.Forms? I found some overview here,…

Cross platform .NET usually means using a native toolkit on each different platform and the result is WPF on Windows, GTK# on Linux, and MonoMac on Mac. The purpose of this is to avoid the uncanny valley of cross platform toolkits like Java Swing at the expense of writing extra UI code.

Some wrappers like Eto.Forms and XWT exist but don't expect drag and drop visual designer tooling.

Thanks to Mono WinForms is sort of cross platform to a certain extent but if you give it a try you'll see why it is not recommended.

Re: Building and Running .NET’s CoreCLR on OS X

#19

Now as .Net becomes more interesting again (for me), can someone comment on the state of GUI app development in .Net? Can I write cross-platform GUI code, or would I need to re-implement the GUI on every platform? Do Windows .Net GUI apps (does that mean Windows.Forms?) work just as-is on Linux (and maybe MacOSX)? What would be the best supported GUI .Net framework? QtSharp? Windows.Forms? I found some overview here,…

I've been messing with Eto.Forms recently. You define everything through code (or optionally in a JSON blob) rather than in a designer, and it tries to use native controls to display your design.

It's pretty solid and easy to use and I'm quite happy with it. If you want an exquisite, beautifully-designed OS X app then you should be looking into having separate frontends per platform anyway, but having tried Eto I find it fits my needs.

It's much better than I expected.

Re: Building and Running .NET’s CoreCLR on OS X

#20

Now as .Net becomes more interesting again (for me), can someone comment on the state of GUI app development in .Net? Can I write cross-platform GUI code, or would I need to re-implement the GUI on every platform? Do Windows .Net GUI apps (does that mean Windows.Forms?) work just as-is on Linux (and maybe MacOSX)? What would be the best supported GUI .Net framework? QtSharp? Windows.Forms? I found some overview here,…

Windows.Forms works. RepetierHost is an example of a cross platform mono forms app.

These days I lean towards web services and using the browser as the GUI.

Post reply on HN