you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 3 years ago* (5 children)

Hi. I am not a game dev, but a c# one. What is it that frustrates you about the dotnet CLI?

Edit: I use C# for work, not a Microsoft employee who works on c# dev lol

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 3 years ago (4 children)

    Documentation is the worst offender. I remember one time that running dotnet restore and later running another command with --no-restore flag wouldn't work, but running the last command without the --no-restore flag would. Creating a sane CI/CD pipeline for C# apps is a PITA.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 7 points 3 years ago

    I've never had an issue with the dotnet CLI, including the commands you're talking about. Their documentation is a bit scattered at times but for the most part they have examples on everything and walk through most scenarios.

    I'm not a Microsoft employee either, just a c# dev of 10 years.

  • source
  • parent
  • [–] 0 points 3 years ago* (2 children)

    I do a lot of work with c# CI/CD and doing what you said absolutely does work.

    Most of my scripts are

    dotnet restore
    dotnet build --no-restore
    dotnet test --no-build
    dotnet publish --no-build
    
  • source
  • parent
  • hideshow 2 child comments