Bernhard Richter

You need to be on dotnet-script 1.0.1 for .Net 5 support `dotnet tool update dotnet-script -g` should bring you up to speed 👍

@jamie-tillman I can't see why not. With `dotnet-script` we can pull in any NuGet package meaning any DI library.

@XenoMustache Could you do a `dotnet script --info` to dump the environment and also provide a sample script that you are having trouble with?

The easiest solution here is to put your dependencies in a NuGet package. For instance ``` #r "nuget:Test,1.0.0" ``` In the `Test` package you reference the `Test2` package and so...

Compilation dependencies are used by OmniSharp to provide language services like Intellisense. It is the runtime dependencies you need to compile and run a script

Not deliberate 😀 Feel free to add a few lines in the doc 👍

This is something I did look into a couple of years ago and back then I could not find a way to pass an `AssemblyLoadContext` to the underlying roslyn scripting...

Really? Wow, that's impressive.👌

This is not something we have discussed, but that isn't to say that it is a bad idea. I don't think we can use `dotnet watch` here since that expects...

Any updates on this?