A strange question, but my boss is an old joke, and he insisted on our coding standards that we do not use C # abbreviations for system types, he likes us to use the full system name. He likes things to be detailed, and I happily follow the standard.
However, the fact that a few months later began to torment me is the fact that the visual studio does not like to conform to the standard when filling out the code. Therefore, if I print:
KeyValuePair<Int32, Object> MyValue = new
Visual studio will finish the rest:
KeyValuePair<int,object>
This is even worse when implementing an interface or abstract class.
This is a minor inconvenience, but nonetheless, and I was wondering if I needed to use a lot of VS options using all the system type names.
I believe that this can be solved using something like Re-Sharper, but, unfortunately, I do not get a license.
EDIT
Yes, he despises the use of the var keyword. I had to state my actual arguments because we mainly develop in C #, but there is a high probability of having to write in C and the C lens, so he doesn’t want us to rely too much on CLR abbreviations, and he also says that will cause less pain when porting code, which to some extent makes sense to me. Its main purpose is to avoid type matches with types such as Int16, Int32, and Int64, but since we follow the standard, it prefers String over string. In fairness, he is a very good coder, if not an old school, but his knowledge of things under the hood is much more than mine, and 90% of the developers who, as I know, come from the gaming background, I think you appreciate the subtlety indicates more . I am always spoiled by the beautiful managed .NET platform.
Many thanks
Floor