@Dennis Can you pull Add++ and Adapt when you can? Adapt's Hello, World! has changed to `Hello, World!`

@Dennis Can you add MoreLinq 3.0 to cs-core?

cd /opt/microsoft/home/csharp
dotnet add package morelinq --version 3.0.0-beta-2

At this point you should run find /usr/share/dotnet/sdk/NuGetFallbackFolder | grep -i morelinq to determine where it put the actual dll

Then add /reference:/usr/share/dotnet/sdk/NuGetFallbackFolder/PATH/TO/DLL to csopts.txt.

You can test if it worked by prepending using MoreLinq; to the C# hello world and seeing if it compiles.

Actually, /opt/microsoft/home/.nuget/packages and not anything in /usr/share

And you have to export HOME=/opt/microsoft/home

What happens when it gets out of beta?

@Dennis Absolutely nothing

You have to manually point it to the new version

._.

If you don't specify version you'll get latest stable

Which is 2.10.0

Which I suppose is fine

And even if it auto-updated, I'd have to change the path in csopts.txt, I guess.

Yep

Do I have manually have to check all my packages for updates? That can't be the only way...

@Dennis You know how in Python you use venv for individual projects, and then pin your packages to a specific version? .NET core assumes that's the only way you'd want to do it and does it for you.

Even though packages are installed "globally" in ~/.nuget, that's only a cache and there's not actually such a thing as a global installation.

So upgrading packages is done manually.

If TIO's C# was based on csproj and not csopts.txt, it would autodetect the path though.

Which I guess would make that be the correct way

And how do we change that? The problem will only get worse with every package I add...

If you want to try switching to csproj, copy the fs-core wrapper but replace the fs with cs.

By the way, do packages work at all with cs-csc?

@Dennis Yeah, you need to specify compiler flags though.

Package names or full paths?

Full paths

So it's unusable for practical purposes.

Since I can't expect my users to know TIO's directory structure.

Also it changes when there's an update

So you get link rot

>_>

This isn't fixable without msbuild

@Pavel I don't get this philosophy at all. If there's a security issue in a package I'm using, it will never get fixed unless I replace it manually.

@Pavel I'm listening.

@Dennis Basically, make /opt/mono/home to mirror /opt/microsoft/home and do a similar configuration there as with .net core

It'd be really complicated

I'll try to work something out

Probably be easiest to maintain a blank project in a seperate git repo you can pull

Ooh, the monodevelop package isn't broken anymore! Just in time.

@cairdcoinheringaahing Done.