4 ms·

Not a competitor. We work closely with the Mono team, specifically Miguel. We are releasing lots of source for them with each .NET Framework release. The Mono t

by runfaster2000 11y ago

Not a competitor. We work closely with the Mono team, specifically Miguel. We are releasing lots of source for them with each .NET Framework release. The Mono team is adopting large quantities of that source to improve Mono. It's a collaboration. Certainly, there are now two .NET choices on Linux. If you ask Miguel, I suspect he'd recommend .NET Core if you are building a server app. Disclosure: .NET Core team member

eatonphil 11y ago
I got confused when trying to install .NET Core, so sorry if this is a bad question. It seemed like .NET Core depended on Mono. Does it actually? I can't remember what exactly seemed like it depended on Mono. Perhaps Nuget? My memory is fuzzy. Either way, these two docs [0,1] (not just those particular pages) could really use some clarifications. I had trouble working my way through either of them and they seemed to be giving conflicting information at times. Granted, I have no significant experience with .NET or Mono. I was able to install Mono once on Ubuntu. But I gave up after trying to install .NET Core on Ubuntu (and FreeBSD) more recently - a week ago. Sorry, I can't provide more substantial criticism right now. I guess the forums[2] would be the best place to bring these issues up in the future (with more information)? [0] http://dotnet.readthedocs.org/en/latest/getting-started/installing-core-linux.html http://dotnet.readthedocs.org/en/latest/getting-started/inst... [1] https://dotnet.github.io/getting-started/ https://dotnet.github.io/getting-started/ [2] http://forums.dotnetfoundation.org/ http://forums.dotnetfoundation.org/
- Locke1689 11y ago
  What's confusing about [1]? I'm not on the ASP.NET team, but may be able to provide some general guidance.
  - eatonphil 11y ago
    It wasn't necessarily that [0] or [1] was confusing in and of themselves but that the information seemed to conflict at times. Having multiple sources can be helpful to establish patterns unless they are saying opposite things. But again, I cannot point to specifics. I guess my current question is, can .NET Core be built on FreeBSD without a Windows machine? It appeared that this, for one, was not the case. This is a bit of a showstopper.
    - voltagex_ 11y ago
      https://github.com/dotnet/coreclr/blob/master/Documentation/building/freebsd-instructions.md https://github.com/dotnet/coreclr/blob/master/Documentation/... - if that doesn't work, it's a bug.
      - eatonphil 11y ago
        So it looks like the answer is yes then. You do need a Windows machine to build the managed components. So I cannot build (for now) if I do not have a Windows machine. I did actually follow this guide, though I still wasn't able to compile. The build failed before the managed components section. If I have a chance to look at it again, I'll try to file a bug report or get more help.
        voltagex_ 11y ago
        Sigh. It'd be really good if MS would give out some Azure time for open source work.

eatonphil 11y ago

I got confused when trying to install .NET Core, so sorry if this is a bad question. It seemed like .NET Core depended on Mono. Does it actually? I can't remember what exactly seemed like it depended on Mono. Perhaps Nuget? My memory is fuzzy. Either way, these two docs [0,1] (not just those particular pages) could really use some clarifications. I had trouble working my way through either of them and they seemed to be giving conflicting information at times. Granted, I have no significant experience with .NET or Mono. I was able to install Mono once on Ubuntu. But I gave up after trying to install .NET Core on Ubuntu (and FreeBSD) more recently - a week ago. Sorry, I can't provide more substantial criticism right now. I guess the forums[2] would be the best place to bring these issues up in the future (with more information)? [0] http://dotnet.readthedocs.org/en/latest/getting-started/installing-core-linux.html http://dotnet.readthedocs.org/en/latest/getting-started/inst... [1] https://dotnet.github.io/getting-started/ https://dotnet.github.io/getting-started/ [2] http://forums.dotnetfoundation.org/ http://forums.dotnetfoundation.org/

Locke1689 11y ago
What's confusing about [1]? I'm not on the ASP.NET team, but may be able to provide some general guidance.
- eatonphil 11y ago
  It wasn't necessarily that [0] or [1] was confusing in and of themselves but that the information seemed to conflict at times. Having multiple sources can be helpful to establish patterns unless they are saying opposite things. But again, I cannot point to specifics. I guess my current question is, can .NET Core be built on FreeBSD without a Windows machine? It appeared that this, for one, was not the case. This is a bit of a showstopper.
  - voltagex_ 11y ago
    https://github.com/dotnet/coreclr/blob/master/Documentation/building/freebsd-instructions.md https://github.com/dotnet/coreclr/blob/master/Documentation/... - if that doesn't work, it's a bug.
    - eatonphil 11y ago
      So it looks like the answer is yes then. You do need a Windows machine to build the managed components. So I cannot build (for now) if I do not have a Windows machine. I did actually follow this guide, though I still wasn't able to compile. The build failed before the managed components section. If I have a chance to look at it again, I'll try to file a bug report or get more help.
      - voltagex_ 11y ago
        Sigh. It'd be really good if MS would give out some Azure time for open source work.