-
-
Notifications
You must be signed in to change notification settings - Fork 84
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 .NET Core 2.0 #39
Comments
There is. Just as soon as I free time up to work on it. Or someone beats me On Nov 11, 2016 23:57, "Cole Mickens" notifications@github.com wrote:
|
I'll also note that currently the .Net Core tooling is in a considerable state of flux so I'm also sort of waiting for it to settle down a bit so the target isn't moving so much. |
coreclr has settled down a bit (w'ere at 2.x.x+ releases now ) Wanted to gauge if anyone is working on this now (or plan to). If there's a branch on this or work in progress, i can help with that too. |
Hi
This was in my plans but I'm doing mostly java right now in the day job and
finding it difficult to get any time to work on this. As a result I don't
think any progress has been made toward coreclr support. I'm wholly
supportive of someone else tackling it. I'd be happy to lend whatever help
I can as time permits.
…On Wed, Jul 5, 2017 at 1:32 PM, salrashid123 ***@***.***> wrote:
coreclr has settled down a bit (w'ere at 2.x.x+ releases now
<https://github.com/dotnet/coreclr/releases> )
Wanted to gauge if anyone is working on this now (or plan to). If there's
a branch on this or work in progress, i can help with that too.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACetw5srBkDlh47RnyiFYKmB9SP9BRXks5sK9aogaJpZM4KwVlb>
.
--
Jeremy Wall
http://jeremy.marzhillstudios.com
Jeremy@marzhillstudios.com
|
hi- I'll spend sometime reading up on this more and also post a question to the bazel users googegroup for assistance as i fear i'm missing fundamentals too. for what its worth, i've started off here...at the moment, it just downloads the dotnet cli and runs a restore command...but the lock files goes somewhere else. If anyone has any comments, pls add it there and i'll work through it. once the bazel rules are done and i can generate a .dll, i've got the 'distroless' baszel-based docker images for coreclr working though. here's the scratchpad i'm working with |
I suppose it makes sense to target .NET Core 2.0 now that it is out. @salrashid123 have you had much success so far? |
I had mixed success (mostly failure) and got a basic build working (just the helloworld, no project-references)... ...but I can't run it because the coreCLR binary requires me to declare a lot of dependencies (eg. libhostfxr.so ) and I don't know how to do that in a general way (thats principally stems from me not knowing bazel beyond beginner level and time to devote to this, really) if you want to try out whatever bit i've done so far,
you'll see the binary is actually generated within the sandbox, but you can't do anything with it:
just FYI, I'll file an issue against docker distroless builds...I was able to make a distroless docker image built and running...but i had to generate the binary by hand...if coreCLR bazel rules actually work, then a proper distroless support is really easy. |
The new toolchain-based implementation supports .NET core. |
This seems to be full .NET Framework with Mono.
The future of .NET seems to be .NET Core. Is there an intent to support .NET Core?
The text was updated successfully, but these errors were encountered: