Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The road towards NetCoreApp2.0

See original GitHub issue

Creating this issue so that we have a place to discuss how to move dotnet script to .Net Core 2.0

In order to support a wider range of NuGet packages, we need to run dotnet script as a netcoreapp2.0

The execution side, dotnet scriptis pretty much working as can be seen in the https://github.com/filipw/dotnet-script/tree/feature/netcore20 branch.

The challenge here is that we also need to update the NuGet package reference support in OmniSharp.Roslyn, so that we can provide proper intellisense for netcoreapp2.0 based scripts.

Version 0.13.0 of dotnet scriptis based upon the new csproj project format where as OmniSharp.Roslyn uses the old project.json format under the hood for resolving NuGet package dependencies.

All the stuff related to resolving dependencies are now in Dotnet.Script.Core and I think we need to split that into a project structure that makes it more reusable from the OmniSharp side of things.

Maybe something like this

Dotnet.Script.Dependencies (common library for both dotnet script and OmniSharp.Roslyn)
Dotnet.Script.Dependencies.Runtime (used by dotnet script for resolving runtime dependencies)
Dotnet.Script.Dependencies.Compiletime (used by OmniSharp.Roslyn to provide compilation metadata references)

to be continued…