Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was looking for a way to disable all caps on Visual Studio and found this post.

It says to add a DWORD registry entry to turn it off:

DWORD: SuppressUppercaseConversion
Value: 1

But my question is, is there something in Visual Studio that looks for a DWORD : SuppressUppercaseConversion and if they find it, they turn off all caps? Or is this some sort of hack that cause the text to no longer be all caps?

If Visual Studio is already looking for this value, why not build it into the options for Visual Studio to turn it on or off?

I've seen this on many other applications, is it just a preference of the developer not to provide these options through their application, but allow you to change them if you know the secret handshake?

share|improve this question

closed as not constructive by Dave M, Renan, 8088, Scott, KronoS Apr 5 '13 at 15:18

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

If Visual Studio is already looking for this value, why not - Lazy developers is the answer, either that or some project manager that killed that feature before the GUI was complete or something... – Zoredache Apr 4 '13 at 18:41
I'm not an authority on the subject, so I'll just comment that you are correct. Presumably they don't automatically add the entry to the registry to keep the hive from growing too fast, and they don't add the option to the Tools|Options... to keep the interface simple. – Ron Apr 4 '13 at 18:43
Its not lazy developers per say it would be simply perhaps an undocumented feature. Projects as complex as Visual Studio do not have features added to them unless they are approved. Its much more likely that the feature exists but it was decided not worth actually supporting – Ramhound Apr 4 '13 at 18:46
Why the downvote? Is it worded poorly, is it a bad question? – guanome Apr 4 '13 at 20:44
up vote 2 down vote accepted

The registry is a database. Programs retrieve values from the database as needed. They can retrieve a single named value. They can retrieve everything in a key or so on. What the program does with the information it retrieves from the registry is completely up to the program.

Most programs Are hard coded to look for a specific entry. Some programs like Windows Explorer are a lot more flexible, in that they will look for entries that conform to certain rules.

share|improve this answer
How do people find out the registry entries to add? Are they developers on the projects? – guanome Apr 4 '13 at 19:04
Documentation, Comments by the applications developers/support teams, Or reverse engineering using something like process explorer or perhaps something that decompiles the program. – Zoredache Apr 4 '13 at 19:19
Alright then, I've always wondered this and didn't find an existing question on here. I think you should add that comment above to the your answer, I think it helps understand the developer's reasoning. – guanome Apr 4 '13 at 19:24
Running something like the strings utility (from systinternals) on an exe is a possible way to find registry key and value names that the program looks for. – Jamie Hanrahan Sep 26 '15 at 15:35

Not the answer you're looking for? Browse other questions tagged .