Hacker News new | ask | show | jobs
by vishbar 3233 days ago
How is the tooling these days? I played with .NET Core a while ago (before the move away from project.json and just after the move to the dotnet command line tool rather than dnx/dnvm/etc.). I found the documentation for the tooling to be confusing, sparse, and often contradictory. Have things improved? How much manual XML munging is required with the new csproj format, assuming one isn't using Visual Studio and is developing on Mac/Linux?
3 comments

It's good, the XML is minimal and looks way better then project.json.
Well it calls home now unless you argue with it ... https://github.com/dotnet/cli/issues/3093
it took me a lot of trial and error, but I was able to get a pretty nice asp net core dev env working with the dotnet cli, and vs code. so its possible, but not always easy.

documentation is still confusing and contradictory, but a little less sparse.

I use the dotnet cli for everything, and rarely need to manually edit the csproj. Even when I do, the csproj is very simple straightforward xml, nothing like the old version.

I use node/npm/gulp tool chain for build pipelines. I set up npm wrappers for the dotnet cli, "npm run build", "npm run test", "npm run start", which I like.

my favorite thing is that I can reasonably work on c# projects without full Visual Studio and solutions.