-
Notifications
You must be signed in to change notification settings - Fork 714
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
Running dotnet cli tools unstable #5
Comments
The library is not targeting xamarin yet, check the project.json. Once we target netstandard the restore errors will dissappear too. Let's move forward not backwards it will be harder to maintain later on. Let's wait for build to see the future of Sharp develop, vs and vs code :) |
The restore errors relate to the dependencies not the library itself. |
Request submitted for Json.Rpc.Client edjCase/JsonRpc#12 to target netstandard 1.1 And more info on netstandard http://dotnet.github.io/docs/libraries/libraries-with-cli.html and mapping support https://github.com/dotnet/corefx/blob/master/Documentation/architecture/net-platform-standard.md |
Anyone who stumbles across this issue with a similar problem can get in contact with me. I have a build script to help compile this project for .Net framework. I may get around to cleaning it up and publishing in a separate repo. |
I will be checking in soon an autogen project / solution file for XS. Also im working on the .net cli support, which I might put in another branch. Try this for ABI |
This could simply be a matter of me not understanding the new toolchain fully, but when I do a
dotnet restore
it fails with lots of errors. When I do adotnet build
it fails. When I do adotnet run
it appears to build all the projects successfully, however when I copy those dlls into my xamarin app I get all sorts of System.Object not referenced errors.Would be nice to have this library as a more traditional csproj style library until dotnet cli is more stable.
The text was updated successfully, but these errors were encountered: