C# editor changing font size on some variables

Anonymous

Microsoft Visual Studio Community 2022

Version 17.12.0 Preview 5.0

VisualStudio.17.Preview/17.12.0-pre.5.0+35424.110

Microsoft .NET Framework

Version 4.8.09032

I have several occurrences of a strange thing in the VS code Editor, C# Project.

The editor is changing the font sizes of some variables in my code, I believe it happens after accepting one or another of the pop up error correction suggestions. These items which have been changed, in the editor, are no longer selectable - any mouse click on them is just ignored. Not ALL accepted error corrections are like this.

Please see short video at HERE. In the video, all I doo is to attempt to select any part of the List<string> in the editor and then paste into an empty line below - as can be seen, it is neither selectable, and is ignored on the Copy attempt.

https://1drv.ms/v/s!AgEpHyV3DNo7g5tjIQ80m3t71AfeBA?e=IuzVuO

Any one shed light on this?

1 answer

Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-13T02:04:06.4466667+00:00
Hi @Anonymous , Welcome to Microsoft Q&A,

Updated:

Maybe during programming, it will suggest you change the type declaration to var and give a message about it.

You can use a #pragma to circumvent these warnings.

You seem to have misunderstood the type you want to copy, it is the type of your variable that VS automatically infers.

It is just a reminder for you, it is not selectable.

If you don't like it, you can disable it in the settings.

When you use the var keyword in your code (such as var myVariable = 10;), Visual Studio will automatically infer the type of myVariable to be int.

Go to Tools > Options.

Under Text Editor > C# > Code Style > General, you can find the relevant options for using var.

Best Regards,

Jiale

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.
Anonymous

2024-11-13T11:42:56.4233333+00:00

Hi

Yes, thank you. In the meantime I did discover that if I remove the 'var' from the statement then everything was fine. Just a bit of strange behavior that I couldn't understand.

Anonymous

2024-11-13T12:03:59.8+00:00

Hi

OK, now, within 5 minutes of accepting you post as Answer. I entered the following line in another Project:

List<string> part2 = new List<string>();

and it has been flagged and listed in the errors pane as "new initialization can be simplified", then if accepted in the pop-up, it changes it to the exact same text, but, with the right hand side 'List<string>' font made smaller and non selectable. To read the text of the line before and after, they are identical - doesn't make sense. What is going on there?

Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-14T01:19:43.79+00:00

As it describes, it can be simplified. But you can choose not to simplify, as I said, you are using var implicit type. This is normal.

Anonymous

2024-11-14T12:11:42.08+00:00

Hi

Maybe just me, but when something is called 'simplified' when all that is evident is to change the font size and make if non selectable, then what is the point?

I sure can see why many choose to stick with other languages. I suppose I will have to spend some time and find out how to suppress these unnecessary changes.

Thanks anyway for trying.

Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-15T01:26:06.11+00:00

The simplification I'm talking about is that your specific type can be simplified to var. You can of course cancel it in the rule table. You can also use the type you want directly without using var. It is used to facilitate coding when we know the type.

Anonymous

2024-11-15T07:35:59.8266667+00:00

Hi

Thanks for sticking with it. However, for me, it is all clear as mud. You are still talking of 'var', and that seemed to be taken care of by simply deleting the 'var' from the statement. My latest issue, from a few posts above is where I started a brand new project and tried to use:

List<string> part2 = new List<string>();

and it has been flagged and listed in the errors pane as "new initialization can be simplified", then if accepted in the pop-up, it changes it to the exact same text, but, with the right hand side 'List<string>' font made smaller and non selectable. To read the text of the line before and after, they are identical - doesn't make sense.

Thanks anyway.

Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-15T07:39:46.86+00:00

Your current comment seems to have strayed from the question of this post.

Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-15T07:40:57.2+00:00

You can choose not to accept the pop-up window, which can also be your choice.

Anonymous

2024-11-15T08:26:14.48+00:00

Hi

No, I have not strayed from the original question, just another example of the same. Also, I do know I do not have to accept anything from a pop up suggestion, but, the whole point of this is that I am (was) trying to fix an error that listed by the system, and using a suggestion provided to do that!

Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-15T08:37:32.8333333+00:00

It does not normally appear as an error.

Anonymous

2024-11-15T11:15:02.2466667+00:00

Hi

I am not seeing the same as you show. In my case:

A new Project with only one single line added. See image, It produces 1 message in the error list. It is different to the error you found.

Viorel 118.4K Reputation points

2024-11-15T17:15:19.23+00:00

If you do not like these Visual Studio interventions and suggestions, displayed with distinct font and background (to differentiate from written code), go to menu, TOOLS, Options, Text Editor, C#, Advanced, and uncheck the “Display inline type hints” options. You can also disable the Syntax Colouring and other features.

To show the hints again, you can press and hold the <Alt+F1>.

In addition, in Error List window, change the dropdown list from “Build + IntelliSense” to “Build Only”

Anonymous

2024-11-15T17:59:50.5966667+00:00

Hi Viorel

The “Build Only” helped. I have been trying out #Pragma statements and the ones I have tried seem to help.

You mentioned “Display inline type hints” but as far as I can see any of the options with similar name(s) are already unchecked. Certainly, if the defaults are unchecked then as I wouldn't have changed them, they would never have been enabled.

Thanks for your help.

Viorel 118.4K Reputation points

2024-11-15T18:09:19.8666667+00:00

If the features related to inline hints are disabled, then the hints that appear in video should not be displayed, maybe excepting the experimental versions of Visual Studio. You can install the recently released Visual Studio 17.12.0.

Anonymous

2024-11-15T19:30:05.6866667+00:00

Hi

I am using:

Microsoft Visual Studio Community 2022 (64-bit) - Preview

Version 17.13.0 Preview 1.0

and these are the options I figured you meant:

Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-18T06:45:28.9733333+00:00

As Viorel said, you can just turn off IntelliSense. Also in the screenshot you provided, it is not presented to you as an error. You can also turn it off using the setting you found.

Anonymous

2024-11-18T12:15:52.21+00:00

Hi

@Jiale Xue - MSFT

Thanks, I am slowly coming to realize that C# is not all that it is made out to be - certainly not straight forward to use. I have been managing to find solutions for a lot of the many warnings/errors/messages that always spring up in any code I write, but there are some that just defy fixing, and, those that are just nonsensical. The one in this thread is an example. There seems to be no explanation of 'what is the difference between the 2 identical code lines with one having been amended with the only visible change being the test size'

This thread was started because I was attempting to deal with those warnings/errors/messages and trying to understand them.

You consistently mention turning off and/or supressing these. I may actually do that and have found some ways to do so, but, it was my intension to try and figure out the meanings of them - seems I will just need to switch off and ignore them.

Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-19T02:03:06.12+00:00

Well, maybe you have some misunderstanding about var. In fact, var is meaningful in many places.

Using var can reduce lengthy type declarations, especially when the type name is long or complex.

Var is very useful when the type is complex or not easy to specify manually. In many cases, using var is optional and is just a syntactic convenience. However, when initializing a variable with an anonymous type, if you need to access the object's properties later, you must declare the variable as var. This is a common scenario in LINQ query expressions. You can mainly check this document. Although var is an implicit type declaration, it is still type-safe. In the use of generic methods or collections, var can simplify the code. So its existence makes sense.

Anonymous

2024-11-19T10:43:32.7933333+00:00

Hi

Although I did have a 'var' in use initially, I quickly found that removing it completely solved the initial problem. Then, using that line of code without the starting 'var' then the error/warning changed to "new initialization can be simplified" which became the subject of this thread as it continued. Although your explanations of the 'var' is valuable, it is no longer (at the moment) any concern.

I will leave this thread now, and instead of accepting any suggested corrections for the "new initialization can be simplified" and use a #pragma to circumvent these warnings.

Thanks for all the help.

Jiale Xue - MSFT 47,581 Reputation points Microsoft Vendor

2024-11-20T03:02:11.4166667+00:00

Now that the original question has been solved, you should accept this one and raise it in a new thread. Q&A forum rules do not allow duplicate questions in a single question. From what I've gotten so far, using #pragma to circumvent these warnings is the answer to your new question, and I'll edit that into my answer.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

C# editor changing font size on some variables

1 answer

Your answer