3 ms·
Naming and version numbers together. I still can't get my head around the series of organisational perversions that would be required to go through that whole p
by bartread 5y ago
Naming and version numbers together. I still can't get my head around the series of organisational perversions that would be required to go through that whole period (lasting years) of .NET/.NET Core/.NET Standard/crazy versioning/divergence and convergence malarkey. This all appears to be on a more sane course now but it's taken far too long.
- d110af5ccf 5y agoI still don't fully understand which parts of the various .NET frameworks I can safely use with a fully FOSS stack on an arbitrary Linux distro or a Mac or whatever and which parts are effectively limited to Windows. The entire thing is incredibly confusing.
- pjmlp 5y agoEasy, the parts that are relevant to sell ASP.NET services on Azure. Everything else is mostly reserved to Windows, including dotnet CLI tooling outcomes like trace and dump files debugging.
- jsmith45 5y ago`dotnet-dump analyze` allows analysis of dumps on Linux using the same SOS debugging commands that work under windbg. They even added some native memory examination commands. You are lacking the rest of a native debugger, but well, asking the team to produce a full blown multi-platform native code debugger would be a bit much. You can instead SOS into lldb for mixed mode debugging of both live processes and dumps on linux. For tracing, well that means very different things to different people. One can capture most of the CLR level events that would go through ETW on windows with the `dotnet-trace` tool, which can also function as a primitive sampling profiler. But despite its name it does not use the profiling apis to implement a tracing profiler. The analysis side of the dotnet-trace tool is subpar, but honestly even the best tools I can find often leave me underwhelmed on the analysis side.