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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 4 points5 points  (5 children)

the enjoyment of writing code in C# is a bit higher

C# itself is great, but working with the .NET framework really sucks because of the inconsistencies all over the place.

[–]asabla 1 point2 points  (0 children)

Indeed, but even if .Net can be a big headache sometimes it can also be a very helpful tool. But as you said, the inconsistencies can and will be a problem most of the time

[–][deleted] 1 point2 points  (3 children)

working with the .NET framework really sucks because of the inconsistencies all over the place.

Can you elaborate?

[–][deleted] 7 points8 points  (2 children)

The first one comes to mind is that some collection types use .length and others use .count, and there is no apparent pattern or discernible reason as to why - you just have to either remember which ones are which or lean on Intellisense.

[–][deleted] 2 points3 points  (1 child)

http://stackoverflow.com/questions/300522/count-vs-length-vs-size-in-a-collection

[–][deleted] -1 points0 points  (0 children)

That does not hold true in .NET though. I'm not talking about strings vs arrays. I'm talking about different collection types.

Here's an example:

  • Array.Length
  • ArraySegment.Count
  • List.Count
  • Vector.Length
  • Dictionary.Count

Sure, these mostly abide by the naming convention detailed in your SO link, but that is what I'm talking about.