Meh. In the end, Microsoft will betray those who trusted it. Long term, better just to pretend it does not exist and never, ever depend on anything with Microsoft name on it.
I knew there'd be at least one of you guys in this thread.
.NET 6 is now in Ubuntu 22.04
251–260 of 351 posts
Re: .NET 6 is now in Ubuntu 22.04
#252Does it come with telemetry enabled by default[1] as the Microsoft binaries do? Or does the Ubuntu version either remove that code or make sure to set the DOTNET_CLI_TELEMETRY_OPTOUT environment variable everywhere? If "Canonical and Microsoft are committed to working together", probably the former. [1] https://docs.microsoft.com/en-us/dotnet/core/tools/telemetry
Yes, telemetry collection is still opt-out. I just tried it.
I am looking at the sources at https://packages.ubuntu.com/source/jammy-updates/dotnet6 and (as far as I can tell) they are applying a patch called 1500sdk-telemetry-optout.patch (originally from Fedora https://src.fedoraproject.org/rpms/dotnet3.1/blob/f36/f/cli-...) that is supposed to make telemetry opt-in.
There's a better fix landing upstream for .NET 7: https://github.com/dotnet/sdk/pull/25935
Re: .NET 6 is now in Ubuntu 22.04
#253Where do you host your .net projects? I am especially interested in anything other than azure webapp and VM's/IIS.
Literally 'dotnet {AppName.dll}' and that's it.
Re: .NET 6 is now in Ubuntu 22.04
#254For reasons currently unclear to me, installing this seems to cause apt to remove Discord. The following packages have unmet dependencies. libc++1-14 : Depends: libunwind-14 (>= 1:14.0.0) but it is not installable libc++abi1-14 : Depends: libunwind-14 (>= 1:14.0.0) but it is not installable E: Unable to correct problems, you have held broken packages.
Ubuntu's .NET runtime relies on libunwind v13. Discord relies on libunwind v14. apt only allows one version of something to installed at once.
Re: .NET 6 is now in Ubuntu 22.04
#255Earlier quoted context omitted.
Old .net has become ".net framework". I'm just glad the number-space has been sorted out. It was annoying to learn that ".NET 2", ".NET Standard 2" and ".NET Core 2" are very different things.
> Old .net has become ".net framework". From my understanding, thats not quite right. AFAIK framework was adapted to differentiate it from standard, core and mono.
https://stackoverflow.com/questions/51390971/im-lost-what-ha...
Re: .NET 6 is now in Ubuntu 22.04
#256Does it come with telemetry enabled by default[1] as the Microsoft binaries do? Or does the Ubuntu version either remove that code or make sure to set the DOTNET_CLI_TELEMETRY_OPTOUT environment variable everywhere? If "Canonical and Microsoft are committed to working together", probably the former. [1] https://docs.microsoft.com/en-us/dotnet/core/tools/telemetry
- Alpine: https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/c...
- Arch Linux: https://github.com/archlinux/svntogit-community/blob/package...
- Fedora: https://src.fedoraproject.org/rpms/dotnet3.1/blob/f36/f/cli-...
- RHEL: https://gitlab.com/redhat/centos-stream/rpms/dotnet6.0/-/blo...
- Ubuntu: http://archive.ubuntu.com/ubuntu/pool/universe/d/dotnet6/dot...
The homebrew build of .NET is the only non-Microsoft build of .NET that seems to keep it enabled (https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/...).
Re: .NET 6 is now in Ubuntu 22.04
#257Earlier quoted context omitted.
I just jumped on the .NET Core gravy train after 6+ years of Ruby on Rails development. I feel so productive and confident working with .NET. Ill be riding this rollercoaster with you for a while!
I'm glad for you, but ActiveRecord is still the best ORM of all time. OF ALL TIME. I rewrote one of my main Rails applications in .NET, and trying to use Entity Framework was like pulling teeth for me, in comparison.
Our Tcl ORM was doing Sybase, SQL Server, DB2, Informix, Oracle and even Access, across Windows 2000/NT, AIX, HP-UX, Solaris, Linux, in 1999 - 2002.
But we never went big into US, so Rails gets the credits.
And we were not alone in this regard, there was Vignette, Cold Fusion, Zope,...
Re: .NET 6 is now in Ubuntu 22.04
#258Question for the experienced .net folks - how is the dev experience of .net on linux vs .net on windows? Is it smooth or clunky? Pretty cool and interesting that a big linux vendor is on board with .net.
It depends a bit on what tools you use, but if you've jumped the ship from VS to VSC and mainly use the dotnet cli for things then there isn't much of a difference between platforms. If you're using VS, as in really use it and all it's feature, there is going to be a massive difference. That being said, I've used .Net and C# for over a decade and it's frankly just a clunky language and toolset. It's gotten better wit…
Not wanting to get in a debate on whether you should use an ORM, but I just don't see anything really special about Gorm that makes the other frameworks "ancient".
When I look at this page: https://gorm.io/docs/advanced_query.html I see the same exact crap that makes me wary of JPA Criteria API.
Re: .NET 6 is now in Ubuntu 22.04
#259I wonder if this opens the door for .NET applications to be included in Ubuntu? Neither this blog post nor Ubuntu’s [1] mention that as a possibility. Just thinking from a Ubuntu package level, where libraries live in packages separate from executables, it might be possible to create library packages using the result of ‘dotnet store’. Then executable packages could reference them when running ‘dotnet publish’. [2] T…
The first part seems to add confidence that if the right apps/developers came along, Canonical themselves likely wouldn't have a problem putting them in the distribution. The second part would explain why there aren't just apps waiting in the wings for it and why "the community" (or at least certain vocal parts) may still not be as welcoming of .NET-based apps in the distribution this time around like it played out that previous time.
Re: .NET 6 is now in Ubuntu 22.04
#260Earlier quoted context omitted.
I knew there'd be at least one of you guys in this thread.
Make us two. I didn't get the memo which states that we need to unconditionally trust Microsoft. We still have copilot case in front of us.
> unconditionally trust Microsoft
But the poster I was responding to was pretty clearly saying that we should:
> unconditionally distrust Microsoft