Подсветка ошибок visual studio - Ремонт и установка крупной бытовой техники

My Visual Studio (2008) Editor has stopped to underline Errors (this nifty wavy red lines). I can’t really tell when, but it can be related to the installation of .Net Framework 3.5 SP 1 or the MVC Beta (which I guess is unlikely). Furthermore have I installed and uninstalled both CodeRush and Resharper for evaluation purposes (decided not to keep either one of them).

Does anyone know the problem and how to restore this functionality again?

Eddie

53.7k22 gold badges124 silver badges144 bronze badges

asked Nov 6, 2008 at 7:21

Have you checked Tools→Options...→Text Editor→C#→Advanced→Underline errors in the editor?

I usually like to reset my settings after messing around with plugins, as they tend to mess with settings: Tools→Import and Export Settings...→Reset all settings.

Spooky

2,9668 gold badges27 silver badges41 bronze badges

answered Nov 6, 2008 at 7:27

sonteksontek

12k12 gold badges49 silver badges61 bronze badges

About possible causes.

For VS 2012 and 2013 if you have more than one instance of Visual Studio on different machines binded to one «live» account and have installed ReSharper on one of them, it disables the native IntelliSense and error underlines (to replace by it’s own rules) that will be synchronised through your account to another machine without ReSharper.

answered May 31, 2014 at 20:29

SerGSerG

1,2414 gold badges18 silver badges37 bronze badges

Found it in Visual Studio 2019 as: Tools > Options > Text Editor > General > Show error squiggles

answered Jan 19, 2021 at 9:22

This is generally called Disable Squiggly or Wavy lines in Visual Studio.

How you will do in Visual studio 2013?

TOOLS -> Options… -> Text Editor -> C/C++ -> Advanced -> Disable Squiggles: True/False (Under IntelliSense) -> Press OK

answered Sep 22, 2016 at 12:12

KulamaniKulamani

4996 silver badges13 bronze badges

I know its an old question, and with various solutions, but I have fixed it in different way. I’m working with Unity3D on my C# code using VS2017, when suddenly VS decides to stop underlining error while im typing. However, if I close the file tab and reopen, it suddenly undelines the error.

For example:

class A { 
public int x; 
s;
}

should obvsiouly give an error for that lonely ‘s’ symbol. But, VS doesn’t underline it until I close and reopen this file tab.

Solution:
Copied the entire Unity Project folder (which is like a regular VS Solution folder basically) and worked with the new folder, which issue was gone there.

answered Sep 29, 2018 at 19:34

MagmusMagmus

2072 silver badges11 bronze badges

For visual studio 2017 act according to HeeJae’s comments in:

https://developercommunity.visualstudio.com/content/problem/113112/design-time-error-checking-isnt-working.html

i.e:

Hi. you are probably hitting a known issue. can you try this?

1.Update to latest release If that doesn’t solve it

2.Go to ToolsOptionsProjects and SolutionsGeneral and uncheck “Allow parallel project initialization”.

3.Close VS.

4.Delete the “.vs” directory beside their solution file.

5.Reopen VS.

thank you

You can re-enable the «Allow parallel project initialization» option after the issue was solved.

I tried to upgrade VS, reset VS settings, clear VS cache and everything people do conventionally but none of them solved this issue! At the end the mentioned solution worked for me magically.

Good luck

answered Apr 3, 2019 at 0:57

user3578181user3578181

1,8962 gold badges17 silver badges12 bronze badges

Unloading and loading same project again from the solution does the trick. Just right click on the project and click «Unload Project». Once unloaded, again right click the same project and click «Reload Project». Error highlighting will return.

answered May 19, 2020 at 23:30

Noor ul AinNoor ul Ain

1822 silver badges16 bronze badges

I had the same issue with 2017. There was a ‘disable intelisense’ option, make sure that is set to false.

answered Jun 8, 2018 at 19:13

For everyone wondering in 2021..

search for «C_Cpp.errorSquiggles» in the settings.

Make sure to have it active for the user, as well as the workspace.
No need to restart Visual Studio.

answered Jan 13, 2021 at 11:40

For me (VS 2019) , after trying the other answers also, setting the scope of analysis from «Current document» to Open document» brought back the missing error markers enter image description here

answered Sep 2, 2021 at 11:19

Just go to settings and search for errors and Image in Error Squiggles. You can see the Error squiggles (Modified: Workspace — Right now you can’t see it because I modified it). Just click on modified and you will see the disabled option. If by mistake you disabled it, just enable it and you can see the red line errors again in your code.

ouflak

2,44810 gold badges44 silver badges49 bronze badges

answered Sep 20, 2021 at 16:13

In latest edition, check for .vscode folder in same project folder. There will be a setting.json file in that. Delete the key value pair of "C_Cpp.errorSquiggles": "Disabled". Restart the vs code.

answered Jul 27, 2022 at 5:14

Источник

Version
Installs
Rating
OpenVSX Downloads

ErrorLens turbo-charges language diagnostic features by making diagnostics stand out more prominently, highlighting
the entire line wherever a diagnostic is generated by the language and also prints the message inline.

Demo image

Features

Highlight lines containing diagnostics
Append diagnostic as text to the end of the line
Show icons in gutter
Show message in status bar

Commands (11)

Command	Description
errorLens.toggle	Error Lens: Toggle (Enable/Disable) Everything (toggle global setting `errorLens.enabled`)
errorLens.toggleError	Error Lens: Enable/Disable Errors in `errorLens.enabledDiagnosticLevels` setting.
errorLens.toggleWarning	Error Lens: Enable/Disable Warnings in `errorLens.enabledDiagnosticLevels` setting.
errorLens.toggleInfo	Error Lens: Enable/Disable Info in `errorLens.enabledDiagnosticLevels` setting.
errorLens.toggleHint	Error Lens: Enable/Disable Hint in `errorLens.enabledDiagnosticLevels` setting.
errorLens.copyProblemMessage	Error Lens: Copy problem message to the clipboard (at the active cursor).
errorLens.copyProblemCode	Error Lens: Copy problem code to the clipboard (at the active cursor).
errorLens.findLinterRuleDefinition	Error Lens: Search in local linter files (like `.eslintrc.json`) for the rule definition.
errorlens.toggleWorkspace	Error Lens: Exclude/Include current workspace by fs path.
errorLens.searchForProblem	Error Lens: Open problem in default browser (controlled by `errorLens.searchForProblemQuery` setting).
errorLens.disableLine	Error Lens: Add a comment to disable line for linter rule.

Settings (55)

Error Lens extension settings start with errorLens.

Setting	Default	Description
enabled	true	Controls all decorations and features (except commands).
enabledInMergeConflict	true	Controls if decorations are shown if the editor has git merge conflict indicators `<<<<<<<` or `=======` or `>>>>>>>`.
fontFamily	«»	Font family of inline message.
fontWeight	«normal»	Font weight of inline message. `"normal"` is alias for 400, `"bold"` is alias for 700).
fontStyleItalic	false	When enabled — shows inline message in italic font style.
fontSize	«»	Font size of inline message (CSS units).
margin	«4ch»	Distance between the last word on the line and the start of inline message (CSS units).
padding	«»	Padding of the inline message. Visible when `#errorLens.messageBackgroundMode#` is set to «message».
borderRadius	«3px»	Border radius of the inline message. Visible when `#errorLens.messageBackgroundMode#` is set to «message».
enabledDiagnosticLevels	[«error», «warning», «info»]	Customize which diagnostic levels(severity) to highlight.
messageTemplate	«$message»	Template used for all inline messages. Whitespace between items is important. List of variables: — `$message` — diagnostic message text — `$count` — Number of diagnostics on the line — `$severity` — Severity prefix taken from `#errorLens.severityText#` — `$source` — Source of diagnostic e.g. «eslint» — `$code` — Code of the diagnostic
messageMaxChars	500	Cut off inline message if it’s longer than this value. (Improves performance when the diagnostic message is long). Set to 0 to disable inline message.
severityText	[«ERROR», «WARNING», «INFO», «HINT»]	Replaces `$severity` variable in `#errorLens.messageTemplate#`.
messageEnabled	true	Controls whether inline message is shown or not (Including background highlight).
messageBackgroundMode	«line»	Controls how inline message is highlighted in the editor (entire line / only message / none).
editorHoverPartsEnabled	{«messageEnabled»:false, «sourceCodeEnabled»:false, «buttonsEnabled»:false}	Controls which parts of the editor hover tooltip to show.
statusBarIconsEnabled	false	When enabled — shows highlighted error/warning icons in status bar.
statusBarIconsPriority	-9000	Move status bar icons left or right by adjasting the number priority.
statusBarIconsAlignment	«left»	Choose on which side the icons status bar is on: left or right.
statusBarIconsUseBackground	true	When enabled — highlights status bar icons with background, when disabled — with foreground.
statusBarIconsAtZero	«removeBackground»	What to do when there are 0 errors/warnings — hide the item or strip its background color.
statusBarMessageEnabled	false	When enabled — shows message in status bar.
statusBarMessagePriority	-10000	Move status bar message left or right by adjasting the number priority.
statusBarMessageAlignment	«left»	Choose on which side the message status bar is on: left or right.
statusBarColorsEnabled	false	When enabled — use message decoration foreground as color of Status Bar text.
statusBarMessageType	«activeLine»	Pick what to show in Status Bar: closest message or only message for the active line.
statusBarCommand	«goToProblem»	Pick command that activates on click for Status Bar.
statusBarMessageTemplate	«»	Template for status bar message. Whitespace between items is important. List of variables: — `$message` — diagnostic message text — `$count` — Number of diagnostics on the line — `$severity` — Severity prefix taken from `#errorLens.severityText#` — `$source` — Source of diagnostic e.g. «eslint» — `$code` — Code of the diagnostic
exclude	[]	Specify messages that should not be highlighted (RegExp). Strings passed to the RegExp constructor: `new RegExp(EXCLUDE_ITEM, 'i');`
excludeBySource	[]	Specify source or source(code) pair that should not be highlighted. Examples: `["eslint"]` or `["eslint(padded-blocks)"]`
excludePatterns	[]	Exclude files by using glob pattern. Example `["*/.{ts,js}"]`
excludeWorkspaces	[]	Exclude workspaces by path.
disableLineComments	{…}	Used for `errorLens.disableLine` command that adds a comment disabling linter rule for a line.
lintFilePaths	{…}	Specify where to search for linter rule definitions by diagnostic source (glob for local linter files). `node_modules` folder is excluded.
searchForProblemQuery	«https://duckduckgo.com/?q=$message»	Pick query to open in default browser when searching for problem with `errorLens.searchForProblem` command.
light		Specify color of decorations for when the light color theme is active.
delay	0	Delay (ms) before showing problem decorations (0 to disable). Minimum delay of 500 is enforced by the extension. New errors will be added with this delay; old errors that were fixed should disappear faster.
onSave	false	When enabled — updates decorations only on document save (manual).
onSaveTimeout	1000	Time period (ms) that used for showing decorations after the document save.
enableOnDiffView	false	Enable decorations when viewing a diff view in the editor (e.g. Git diff).
followCursor	«allLines»	Highlight only portion of the problems.
followCursorMore	0	Augments `#errorLens.followCursor#`. Adds number of lines to top and bottom when `#errorLens.followCursor#` is set to `activeLine`. Adds number of closest problems when `#errorLens.followCursor#` is `closestProblem`
gutterIconsEnabled	false	When enabled — shows gutter icons (In place of the debug breakpoint icon).
gutterIconsFollowCursorOverride	true	When enabled and `#errorLens.followCursor#` setting is not `allLines`, then gutter icons would be rendered for all problems. But line decorations (background, message) only for active line.
gutterIconSize	«100%»	Change gutter icon size. Examples: `auto`, `contain`, `cover`, `50%`, `150%`.
gutterIconSet	«default»	Change gutter icon style.
errorGutterIconPath	«»	Absolute path to error gutter icon.
warningGutterIconPath	«»	Absolute path to warning gutter icon.
infoGutterIconPath	«»	Absolute path to info gutter icon.
errorGutterIconColor	«#e45454»	Error color of `circle` gutter icon set.
warningGutterIconColor	«#ff942f»	Warning color of `circle` gutter icon set.
infoGutterIconColor	«#00b7e4»	Info color of `circle` gutter icon set.
removeLinebreaks	true	When enabled — replaces line breaks in inline diagnostic message with whitespaces.
replaceLinebreaksSymbol	«⏎»	Symbol to replace linebreaks. Requires enabling `#errorLens.removeLinebreaks#`.
scrollbarHackEnabled	false	When enabled — prevents showing horizontal scrollbar in editor (caused by inline decorations).

Colors (26)

Can be specified in settings.json (workbench.colorCustomizations section)

Color	Dark	Light	HC	Description
errorLens.errorBackground	`#e454541b`	`#e4545420`	`#e454541b`	Background color of the entire line containing error.
errorLens.errorMessageBackground	`#e4545419`	`#e4545419`	`#e4545419`	Background color of the error message.
errorLens.errorBackgroundLight	`#e4545420`	`#e4545420`	`#e4545420`	Background color of the entire line containing error (Only in light themes).
errorLens.errorForeground	`#ff6464`	`#e45454`	`#ff6464`	Text color used to highlight lines containing errors.
errorLens.errorForegroundLight	`#e45454`	`#e45454`	`#e45454`	Text color used to highlight lines containing errors (Only in light themes).
errorLens.warningBackground	`#ff942f1b`	`#ff942f20`	`#ff942f1b`	Background color used to highlight lines containing warnings.
errorLens.warningMessageBackground	`#ff942f19`	`#ff942f19`	`#ff942f19`	Background color of the warning message.
errorLens.warningBackgroundLight	`#ff942f20`	`#ff942f20`	`#ff942f20`	Background color used to highlight lines containing warnings (Only in light themes).
errorLens.warningForeground	`#fa973a`	`#ff942f`	`#fa973a`	Text color used to highlight lines containing warnings.
errorLens.warningForegroundLight	`#ff942f`	`#ff942f`	`#ff942f`	Text color used to highlight lines containing warnings (Only in light themes).
errorLens.infoBackground	`#00b7e420`	`#00b7e420`	`#00b7e420`	Background color used to highlight lines containing info.
errorLens.infoMessageBackground	`#00b7e419`	`#00b7e419`	`#00b7e419`	Background color of the info message.
errorLens.infoBackgroundLight	`#00b7e420`	`#00b7e420`	`#00b7e420`	Background color used to highlight lines containing info (Only in light themes).
errorLens.infoForeground	`#00b7e4`	`#00b7e4`	`#00b7e4`	Text color used to highlight lines containing info.
errorLens.infoForegroundLight	`#00b7e4`	`#00b7e4`	`#00b7e4`	Text color used to highlight lines containing info (Only in light themes).
errorLens.hintBackground	`#17a2a220`	`#17a2a220`	`#17a2a220`	Background color used to highlight lines containing hints.
errorLens.hintMessageBackground	`#17a2a219`	`#17a2a219`	`#17a2a219`	Background color of the hint message.
errorLens.hintBackgroundLight	`#17a2a220`	`#17a2a220`	`#17a2a220`	Background color used to highlight lines containing hints (Only in light themes).
errorLens.hintForeground	`#2faf64`	`#2faf64`	`#2faf64`	Text color used to highlight lines containing hints.
errorLens.hintForegroundLight	`#2faf64`	`#2faf64`	`#2faf64`	Text color used to highlight lines containing hints (Only in light themes).
errorLens.statusBarIconErrorForeground	`#ff6464`	`#e45454`	`#ff6464`	Status bar icon item error color. Foreground is used when the `errorLens.statusBarIconsUseBackground` setting is disabled.
errorLens.statusBarIconWarningForeground	`#fa973a`	`#ff942f`	`#fa973a`	Status bar icon item error color. Foreground is used when the `errorLens.statusBarIconsUseBackground` setting is disabled.
errorLens.statusBarErrorForeground	`#ff6464`	`#e45454`	`#ff6464`	Status bar item error color.
errorLens.statusBarWarningForeground	`#fa973a`	`#ff942f`	`#fa973a`	Status bar item warning color.
errorLens.statusBarInfoForeground	`#00b7e4`	`#00b7e4`	`#00b7e4`	Status bar item info color.
errorLens.statusBarHintForeground	`#2faf64`	`#2faf64`	`#2faf64`	Status bar item hint color.

Line highlighting depends on the "errorLens.messageBackgroundMode" setting.

#fff0 — Completely transparent color.

Upstream issues

Please upvote the following VS Code issues:

Api for editor insets
Access theme’s colors programmatically
When completing color keys in settings, fill in current value
Inline text adornments break word wrapping
OnClick event on Gutter
Support hover decorations over the line numbers i.e. gutter

Источник

Visual Studio Code — недавно поставил, осваиваю, вроде пока не тупит как Breackets.

В старой программе у меня ошибки подсвечивались, если допустим лишний див поставлю или не закрою див правильно или в css скобку не поставлю и т.д, у меня подсвечивало и видно было что есть ошибка в коде.

В Visual Studio Code — пока такого не сделал, хотя поставил плагин, HTMLHint, он не подсвечивает.

Я открыл страницу index.php, там у меня hmtl, js, php.
Может по этому HTMLHint не срабатывает, хотя должно по идеи работать.

Хотелось бы чтоб так подсвечивало:

Проверял css, там есть подсветка, волнистая оранжевая линия, как ее можно изменить? а то не очень и приметно что ошибка. Желательно изменить так чтобы красным шрифт выделялся, как реализовать?

Вот так в css подсвечивает.

Что заметил, почему teg font подсвечивает, пока не могу понять из-за ошибки что не должно быть такого тега в html, хотя ерунда же.

В шаблоне в стилях для ошибок (если я правильно понял стиль для подсветки ошибок)

{
      "name": "Invalid",
      "scope": "invalid",
      "settings": {
        "fontStyle": " bold underline",
        "foreground": "#ff0000"
      }
    },
    {
      "name": "Invalid deprecated",
      "scope": "invalid.deprecated",
      "settings": {
        "foreground": "#ff0000",
        "fontStyle": " bold underline"
      }
    },

Источник

Does anyone know the problem and how to restore this functionality again?

Eddie

53.7k22 gold badges124 silver badges144 bronze badges

asked Nov 6, 2008 at 7:21

Have you checked Tools→Options...→Text Editor→C#→Advanced→Underline errors in the editor?

I usually like to reset my settings after messing around with plugins, as they tend to mess with settings: Tools→Import and Export Settings...→Reset all settings.

Spooky

2,9668 gold badges27 silver badges41 bronze badges

answered Nov 6, 2008 at 7:27

sonteksontek

12k12 gold badges49 silver badges61 bronze badges

About possible causes.

answered May 31, 2014 at 20:29

SerGSerG

1,2414 gold badges18 silver badges37 bronze badges

Found it in Visual Studio 2019 as: Tools > Options > Text Editor > General > Show error squiggles

answered Jan 19, 2021 at 9:22

This is generally called Disable Squiggly or Wavy lines in Visual Studio.

How you will do in Visual studio 2013?

TOOLS -> Options… -> Text Editor -> C/C++ -> Advanced -> Disable Squiggles: True/False (Under IntelliSense) -> Press OK

answered Sep 22, 2016 at 12:12

KulamaniKulamani

4996 silver badges13 bronze badges

For example:

class A { 
public int x; 
s;
}

should obvsiouly give an error for that lonely ‘s’ symbol. But, VS doesn’t underline it until I close and reopen this file tab.

Solution:
Copied the entire Unity Project folder (which is like a regular VS Solution folder basically) and worked with the new folder, which issue was gone there.

answered Sep 29, 2018 at 19:34

MagmusMagmus

2072 silver badges11 bronze badges

For visual studio 2017 act according to HeeJae’s comments in:

https://developercommunity.visualstudio.com/content/problem/113112/design-time-error-checking-isnt-working.html

i.e:

Hi. you are probably hitting a known issue. can you try this?

1.Update to latest release If that doesn’t solve it

2.Go to ToolsOptionsProjects and SolutionsGeneral and uncheck “Allow parallel project initialization”.

3.Close VS.

4.Delete the “.vs” directory beside their solution file.

5.Reopen VS.

thank you

You can re-enable the «Allow parallel project initialization» option after the issue was solved.

I tried to upgrade VS, reset VS settings, clear VS cache and everything people do conventionally but none of them solved this issue! At the end the mentioned solution worked for me magically.

Good luck

answered Apr 3, 2019 at 0:57

user3578181user3578181

1,8962 gold badges17 silver badges12 bronze badges

answered May 19, 2020 at 23:30

Noor ul AinNoor ul Ain

1822 silver badges16 bronze badges

I had the same issue with 2017. There was a ‘disable intelisense’ option, make sure that is set to false.

answered Jun 8, 2018 at 19:13

For everyone wondering in 2021..

search for «C_Cpp.errorSquiggles» in the settings.

Make sure to have it active for the user, as well as the workspace.
No need to restart Visual Studio.

answered Jan 13, 2021 at 11:40

For me (VS 2019) , after trying the other answers also, setting the scope of analysis from «Current document» to Open document» brought back the missing error markers enter image description here

answered Sep 2, 2021 at 11:19

ouflak

2,44810 gold badges44 silver badges49 bronze badges

answered Sep 20, 2021 at 16:13

In latest edition, check for .vscode folder in same project folder. There will be a setting.json file in that. Delete the key value pair of "C_Cpp.errorSquiggles": "Disabled". Restart the vs code.

answered Jul 27, 2022 at 5:14

Источник

VS 2019 — Enable «Underline errors in the text editor»

So out of nowhere, VS just stopped underlining errors in my code. For instance, I have the following code snippet that has no squiggly lines:

using System;

namespace GradeBook
{
    public class Book()
    {
        int x = "L";
    }
}

Googling the problems tells me that there should be a setting found by navigating to Tools > Options > Text Editor > C# > Advanced > Underline error in text editor. However, I cannot locate the «Underline error in text editor» option.

I have tried resetting the settings, but to no avail.

Does anyone know how I can the squiggly lines back?

Источник