From: "Till Wegmüller" <toasterson@gmail.com>
To: developer@lists.illumos.org
Subject: Re: [developer] dotnet on illumos?
Date: Wed, 12 Jun 2024 19:58:22 +0200 [thread overview]
Message-ID: <f881e962-c55a-423a-8f6e-bab89c2f3a7c@gmail.com> (raw)
In-Reply-To: <ZmnUYocgoPBE5Gal@mnx.io>
On 12.06.24 19:01, Jonathan Perkin wrote:
> * On 2024-06-12 at 17:49 BST, Till Wegmüller wrote:
>
>> Thats all I remember. Maybe others remember more?
>
> Older pkgsrc branches have mono 4.x, for example:
>
>
> https://pkgsrc.smartos.org/packages/SmartOS/2020Q4/x86_64/All/mono-4.0.4.1nb23.tgz
>
> which as far as I'm aware worked ok, however I assume this only useful
> for older .Net software?
Not just older, You need to be straight up ancient for mono runtime. I
had to switch a server to linux 7 years ago, due to us missing dotnet
core support.
>
> We always attempt to build the latest version of lang/mono, but it
> obviously fails:
>
>
> https://us-central.manta.mnx.io/pkgsrc/public/reports/upstream-trunk/20240611.2249/mono-6.12.0.199nb1/build.log
It seems that it's a seperate runtime from dotnet core. And mono having
limited support for ASP.NET seems like a bad thing. dotnet core it the
default runtime and OSS. My vote would be on the dotnet runtime and not
mono. At my current Job all dotnet apps use dotnet core. Mono is not
used at all for a long time.
next prev parent reply other threads:[~2024-06-12 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 19:56 Gordon Ross
2024-06-12 16:47 ` [developer] " Till Wegmüller
2024-06-12 17:01 ` Jonathan Perkin
2024-06-12 17:58 ` Till Wegmüller [this message]
2024-06-12 18:22 ` Jason King
2024-06-12 19:20 ` Till Wegmüller
2024-06-12 18:00 ` Jason King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f881e962-c55a-423a-8f6e-bab89c2f3a7c@gmail.com \
--to=toasterson@gmail.com \
--cc=developer@lists.illumos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).