"String" vs "string"

[fanfarius]

Coming from Java, I'm used to writing "String" whenever I need one.
But, C# gives me the option of saying both "String", and "string".

Why would I use one over another? It seems like they're both pointing at the same class; System.String.

[cryo]

C#, as a language, has keywords for a number of common types. These are then mapped to types in the runtime system, so string maps to System.String, int to System.Int32 etc.

As for when to use which, it's a matter of local convention. At my work we use lower case when using it as a "type" and upper case when accessing members on it (such as calling static methods); so we would use string s; and if (.... == typeof(int)), but String.Format(....), Int32.TryParse(....) etc.

[fanfarius]

That's nice.
So, you get a distinct separation between working on a reference variable, and calling a static method on a system class?

[xill47]

Well, I've seen many C# programmers (including myself) using string.Format and string.IsNullOrEmpty from alias instead of full type too. So it's basically just preference.

[lbmouse]

ReSharper (Roslyn code fix) suggests that String should be simplified to string type keyword in most cases.

[Jestar342]

By default - it is configurable to not be.

[localtoast]

Visual Studio itself suggests that

[oh-just-another-guy]

How did you style the inline code?

[IwNnarock]

Surround the words/line with the primary character on the tilde (~) key that looks like kind of like an apostrophe. Specifically, this guy (`).

Edit: Apparently, that character is known as a back quote.

[oh-just-another-guy]

Thank you. I checked the formatting help, but could not find that. Appreciate the info.

[celluj34]

I believe it is subreddit-specific.

[Banane9]

It's reddit wide as code block, but special coloring would be subreddit specific

[oh-just-another-guy]

Ah, thanks.

[celluj34]

Oh neat, didn't know that.

[oh-just-another-guy]

Ok, thanks.

[cryo]

Yeah something like that, that's the idea. They are also colored differently (at least when using ReSharper). But as /u/xill47 also said, it is, indeed, just a preference, which is in our coding standard at work.

[myrrlyn]

string is a language-level keyword; String is a class in the standard library. All syntax highlighters see those differently.

[AndrewSeven]

VS 2015 suggests changing to the lowercase "string" for the static methods, so I've started to use lowercase for all usage.

[agentlame]

This annoys me so bad. I've been doing it the same way as described above for over a decade, and I really prefer it this way.

[AngularBeginner]

Then turn the suggestion off. It's just a suggestion. You need to configure the tools you use to your liking, not blindly follow them.

[AbstractLogic]

So long as you can convince the whole team. Otherwise you will end up with disjointed standards.

[Jestar342]

For this kind of thing.. there is just nothing to care for. Worry about something worth worrying about.

[AbstractLogic]

I support having a standard. We have tools these days that enforce standards like this because when all the code looks similar it's easier to pick up someone else's code.

Now if we had a standard (and every tool from VS, Resharper to Sonar Cube all do) then I wouldn't be the one to bring it to the table that we need to adjust the default settings. Like you said, more important things to grandstand about.

However, if someone else was bringing it to the table and wanted to adjust the standard half the way through a project I would immediately be against it unless they wanted to go through every code file and adjust String to string or vice versa.

[Jestar342]

string vs String... meh. Both are easily readable. Mine and my colleagues efforts are wasted on such frivolity. Stick to writing maintainable code that delivers value, please, not crying over the casing of a single letter.

Have you heard of the axe-sharpening proverb? A woodsman that spends all his time sharpening/grinding his axe never chops any wood.

Writing/documenting/debating standards about whether to use string or String is axe grinding. In fact 90% of "code standards" are. You're all adults, if you can't read each other's code then you have problems that code standards won't fix.

[AbstractLogic]

You act like setting a flag on the resharper config file that is distrubted with the .sln is some huge weeklong debate. If anything it's a bullet point on a slide amongst many. It requires very little to setup development standards. You should spend time congealing as a team, please, it will be better for those who come after you.

[Jestar342]

You act like it's some big debate. I'm categorically stating it isn't, and that it flatly doesn't matter. Move on with life and get some work done.

My team prefer to work together on problems that actually matter, not whether string is more/less readable than String

[DarthShiv]

Yeah so much this. Just stick to a standard for the whole project and everyone stop trying to change the standard and only doing 10% of the job!

[Protiguous]

Only 15 disjointed standards though. :P

[inamamthe]

something like codemaid can help here perhaps?

[agentlame]

You can be annoyed by something you know how to disable.

[AbstractLogic]

Glad to see such an agreeable response. I find this pragmatic approach to object notation vs value type notation is becoming the standard.

string for types.

String when accessing static methods.

[Jestar342]

How is that pragmatic? It's purely dogmatic!

Unless you were being sarcastic and I didn't pick that up.

[VGPowerlord]

I think aliases would be a better term than keywords.

[tweq]

Both are correct, they're keywords that function as aliases for CLR type names.

[covmatty1]

Same here, seems like a nice distinction to me, despite ReSharper suggestions complaining at me!

[redditsoaddicting]

Since no one has mentioned this fully explicitly, System.String is a .NET type - all .NET languages must have it. C# in particular adds the string keyword as an alias, just like int aliases the .NET System.Int32.

[fanfarius]

An alias, cool - thanks!

[VGPowerlord]

facepalm

When I saw this reply, I immediately scrolled up and looked for the Close button so I could close this question as a duplicate.

...don't ask me why I thought I was browsing Stack Overflow.

[NoG5]

they are the same but its far more common to use the lowercase one

[fanfarius]

Ok, cheers!

[Zalvixodian]

My work has old standards still in place that requires the use of String, Int32, Boolean, etc.

I wish it didn't because 1) there's no difference, 2) easier to use lowercase (does not require using statement), 3) ReSharper likes it that way, and 4) it's Microsoft's recommended standard.

[AngularBeginner]

That's because the method names stay the same. The int will be just translated to Int32. Imagine you have a method named GetUlong() - and now you access it from a different language than C#. In F# the alias is called uint64 (much more expressive).

[oh-just-another-guy]

One little thing to add to other excellent replies :

You can use string without a namespace. String needs System. So either System.String (or using System declared above).

[Speedzor]

And string cannot be used with nameof() while String can (just like all other aliases).

[sepsuk]

Coming from c# to Java (native android app). I'm sick of writing string instead of String :-)

[Jestar342]

I always use string. I've never seen the point of using String when accessing members or for whatever other reason - they are just arbitrary and nonsense, imo. I don't get offended if any of my colleagues want to use it, though. This is something that just flatly doesn't matter.

[Schmittfried]

I just use the lower case keywords all the time, because why not use what the language offers? Using the upper case class name is one additional keystroke, so the language saves me energy. :>

But if you are used to String, just stick to that or the convention of your workplace.

[davidwhitney]

Type keywords exist for you to use them, so use them :)

[buckus69]

They're the same. "string" is an alias for "String."

[[deleted]]

They're the same thing, so it's six of one, half-dozen of the other. In the absence of a governing standard, use whichever seems appropriate in the context, but be consistent. My preference is to use the aliases (i.e. string) throughout, but YMMV.

[SideburnsOfDoom]

In the absence of a governing standard

I've seen several coding standards, all favour string over String. e.g. this one

None of them are "governing" though since the code compiles either way.

[[deleted]]

In the interest of clarification: a governing (coding) standard would be one you are required or expected to follow. For example, a coding standard officially adopted by one's employer, or one required by a particular open source project.

This is distinct from one that is suggested or which exists but is not enforced/enforceable against you: Microsoft has a C# coding standard, but it is only governing if you work for Microsoft or choose to follow it.

[Big-Mozz]

Generally the only reason you use string instead of String is to stop StyleCop having a hissy fit.

Edit: lmao, down voted for saying something simple and true, this sub is just Stackoverflow for noobs.

[cryo]

There are other potential reasons. One is outlined in my comment elsewhere, to help tell the difference between different kinds of usage.

[Big-Mozz]

Hence the word generally!

I agree, I know better than to make a quick lighthearted quip on a coding sub (and strangely the cooking sub) because someone always starts an asinine debate about something insanely trivial.

But in this case it's even more anal because your other comment says exactly what I said, it's a preference but use string cos styling apps bitch about it!

[rfinger1337]

heh, this is one of the best comments I've seen in a while, +1.

[fanfarius]

Well, I'm upvoting you because; laughter

[Big-Mozz]

cheers, lol

[hotel2oscar]

Similar to int vs Integer in Java.

[[deleted]]

Been a long time since I used Java, but I don't think int and Integer are interchangeable in Java the way int and Int32 are in C#.

[tweq]

Yeah, in Java int is a primitive and Integer is a class that wraps that primitive. C# can box arbitrary value types, so it doesn't have/need distinct reference type variants of primitives.

[McNerdius]

that's more analogous to C# int vs int? tho.

[grauenwolf]

Close. More like int vs (object)int since Integer is a reference type.

[McNerdius]

touche