Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support dotnet core (update to latest TPSDK) #188

Closed
mateuszlewko opened this issue Oct 16, 2017 · 9 comments
Closed

Support dotnet core (update to latest TPSDK) #188

mateuszlewko opened this issue Oct 16, 2017 · 9 comments
Labels

Comments

@mateuszlewko
Copy link

Is there any support planned for .net core (2.0)?

Currently when I do dotnet build, I get:

/opt/dotnet/sdk/2.0.0/FSharp/Microsoft.FSharp.Targets(224,9): error MSB6006: "RunFsc.sh" exited with code 134. [<path to fsproj>]

Maybe it's relatively easy to fix this issue (I have no idea what it means)?

@dsyme
Copy link
Member

dsyme commented Oct 27, 2017

@mateuszlewko See dotnet/fsharp#3303.

@tpetricek This type provider may also need to be updated to use the latest Type Provider SDK (i.e. updating ProvidedTypes.fs etc)

@mateuszlewko
Copy link
Author

mateuszlewko commented Oct 30, 2017

Thanks for the link, however it seems it's not working for me.
When I do dotnet build I get this error:

error FS3053 : The type provider 'RProvider.RProvider' reported an error : The type provider constructor has thrown an exception: Connection refused
Build FAILED.

I have another (mono) project on same machine which builds fine.
Also I can see this error while building and in vs code:

RProvider.dll has assembly level attribute 'Microsoft.FSharp.Core.CompilerServices.TypeProviderAssemblyAttribute' but no public type provider classes were found

Type provider error in vs code:

The type provider 'RProvider.RProvider' reported an error: The type provider constructor has thrown an exception: Unix transport error.

@dsyme Do you know what could cause Unix transport error? Is it something with RProvider + dotnet core or is just my machine setup?

@rj-xy
Copy link

rj-xy commented Apr 23, 2018

+1

@dsyme dsyme changed the title Support dotnet core Support dotnet core (update to latest TPSDK) Jul 18, 2018
@dsyme dsyme added the Type: Enhancement New feature or request label Jul 18, 2018
@daz10000
Copy link

Is there anything I can do to help with this? I just showed Rprovider to a new F# user and we are using dotnet core for everything at this point. Building hello world fails with this error. I am guessing that updating to latest SDK and compiling against netstandard2.0 would fix this. We have recently had good outcomes with our postgres type provider and dotnet core. Thoughts?

Darren

error FS3053 : The type provider 'RProvider.RProvider' reported an error : The type provider constructor has thrown an exception: Exception has been thrown by the target of an invocation. [C:\extproj\Rexample\Rexample.fsproj]
FSC : warning FS3005: Referenced assembly 'C:\Users\user\.nuget\packages\rprovider\1.1.21\lib\net40\RProvider.dll' has assembly level attribute 'Microsoft.FSharp.Core.CompilerServices.TypeProviderAssemblyAttribute' but no public type provider classes were found [C:\extproj\Rexample\Rexample.fsproj]

My hello world Program.fs is just from the example

open System
open FSharp.Data
open RProvider
open RProvider.``base``
open RProvider.graphics

[<EntryPoint>]
let main argv =

    let data = [ for x in 0.0  .. 0.1 .. 10.0 -> x * cos x]
    R.plot data
    0 // return an integer exit code

Project file is just

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.1</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <Compile Include="Program.fs" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="Rprovider" Version="1.1.21" />
  </ItemGroup>

</Project>

@dsyme
Copy link
Member

dsyme commented Oct 18, 2018

The problem is R.NET which needs to be moved to .NET Standard. However the project hasn't had a commit for a year. I've raised the issue of sustainable project maintenance for R.NET.

@daz10000
Copy link

Ah, the rabbit hole is deep in this one. provider on top of R.Net on top of C library mixed in with some optimization opportunities and a corporate / open source angle. Seems like a quick fix ;) - happy to be helpful in any way

@jmp75
Copy link
Contributor

jmp75 commented Apr 22, 2019

I've explored on a branch of my fork migrating RProvider to prerelease packages for R.NET that now target netstandard2.0. I am confused by paket and have not yet found a way to compile RProvider - help wanted.

@toburger
Copy link

toburger commented Jan 7, 2020

Any progress regarding this issue?

@AndrewIOM
Copy link
Collaborator

Closing as .net 5 support merged in #210

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants