Move to csproj?

[dotnet-script]

Move to csproj?

[filipw]

This is great. I think we can support both for the time being for the sake of sanity - but would you be willing to open a PR or should I? 😄

[seesharper]

Sorry for the late reply. Currently in vacation mode and will be for another couple of weeks. If you want to get the ball moving before that you can take a look here. I have this CSX project that is basically nothing but a place where I experiment with scripting stuff :)
https://github.com/seesharper/csx/blob/master/src/RuntimeDependencyResolver.cs

[seesharper]

I've started to look into this a bit more and we can easily support both project.json and csproj simultaneously. The best approach would probably be to use csproj behind the scenes for project-less contexts. Then we would no longer rely on NuGet350 to resolve Nuget Packages. All we need for package resolving at the execution side (dotnet script) is the dotnet cli. Having it work with an "user defined" csproj file is a step further down the road as it would require changes in omnysharp-roslyn. I doing a spike now on how to get csproj support into dotnet script for project-less contexts. Omniharp-roslyn could also quite easily be updated to support csproj based scripts at least as long as we target netcoreapp where we can pull the dependency graph from the Microsoft.Extensions.DependencyModel.

[seesharper]

The goal is to have this script work on Windows and *nix platforms.

#r "nuget:Microsoft.Data.SQLite, 1.1.1"
using Microsoft.Data.Sqlite;

using (var connection = new SqliteConnection("Data Source=:memory:"))
{
    connection.Open();
}

This involves loading native libraries as well as assembly redirecting.
If we can load and execute this script, we should be able to consume just about any package.

[seesharper]

Covered by the 0.13.0 release