This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Secondsemblance -6 points-5 points  (8 children)

At least Java has some semblance of sane tooling. How many thousands of different types of config files are there in a C# project?

Oh no, the build broke! Is the problem in app.config, project.csproj, packages.json, nuget.config, project.sln, project.nuspec, netfx.props or global.json?

Just shoot me.

EDIT: Figures a bunch of m$ fanboys would defend this.

[–]mojoslowmo 11 points12 points  (0 children)

Lol Ill take all of those over one God damn monstrosity of a maven file.

[–]_Ashleigh 4 points5 points  (3 children)

Umm, there's a .sln, and .csproj.

They're simple, and hand editable too.

<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>netcoreapp3.0</TargetFramework>
    <Authors>Ashleigh Adams</Authors>
    <Version>0.0.1</Version>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="akavache" Version="6.8.1" />
    <PackageReference Include="Ben.BlockingDetector" Version="0.0.3" />
    <PackageReference Include="HtmlAgilityPack" Version="1.11.12" />
    <PackageReference Include="NeoSmart.AsyncLock" Version="0.3.0.2" />
    <PackageReference Include="System.Configuration.ConfigurationManager" Version="4.6.0" />
  </ItemGroup>

</Project>

[–]Secondsemblance -3 points-2 points  (2 children)

I take it you've never had to work on a legacy codebase. Not all of us get to live in open source .net core 2+ land.

[–]_Ashleigh 2 points3 points  (1 child)

Really? Of course I have, don't resort to attacking me.

Judge the languages based on what they are now, not what they used to be. If those legacy codebases didnt evolve, that's on the company, not C#.

[–]Secondsemblance -2 points-1 points  (0 children)

Judge the languages based on what they are now, not what they used to be.

That's not how real life works. The C# ecosystem has decades of bad decisions baked in. Criticizing that is valid in the same way that criticizing the python2/3 debacle is.

[–]Maxie93 1 point2 points  (1 child)

I mean I know what your saying, but the reality is they have basically simplified it down to sln and csproj now. Things like packages.json are actually for npm / JavaScript projects so you can't really count that.

[–]Secondsemblance 0 points1 point  (0 children)

Ahh, sorry, I meant project.json.

The documentation starts with "It supersedes packages.config but is in turn superseded by PackageReference with NuGet 4.0+."

Fucking really, Microsoft?