I am using a VS 2017. a "Debugger, Getting a datatip text" window keep poping up when a project being run.
There is no use for data tips in the typescript files in my project. Is it possible to prevent that window poping up specifically in typescript files?
It gets really frustrating...
Go to Tools -> Options -> Debugging -> General and uncheck the option 'Enable property evaluation and other implicit function calls'
Hope this helps you
Related
I'm using visual studio to edit a basic webpage I'm making, which uses the VisJS library. Intellisense magically works:
However, on that same object when I try to 'Go To Definition', it can't find it:
It would also be really nice to see what parameters the Network constructor takes as well.
How do I get this to work?
I experienced a similar problem on Visual Studio 2017, where Go To Definition wasn't working with JavaScript files.
The solution was going to:
Tools > Options > Text Editor > JavaScript/TypeScript > Language Service
There are 2 checkboxes there, one of them is:
Disable dedicated syntax process (restart required)
I unchecked it, restarted VS, and F12 then worked as usual.
I'm working on a project and suddenly the debug ignore my breakpoints and doesn't debug,
Make sure the dropdown near on the debug toolbar shows "Debug" and not "Release".
In case you need to "hit" the break point in "RELEASE" mode go to:
Tools -> Options -> Debugging -> General and UN-CHECK "Just my code" option, in order to enable loading symbols and actualy hitting a break point ;)
Sometimes Visual Studio just gets all confused. I've found restarting Visual Studio, unsetting/resetting breakpoints, and commenting out the places where it's falling over all help to trip Visual Studio into working again.
Visual Studio can be quite slow to open and work with. The menus and auto-hide windows can get sluggish and commands take a while to start. What are the list of things one can do to make the UI of Visual Studio load faster and operate faster? What settings can one change to make it feel lean and minimal?
PS: I know Visual Studio Express is way leaner and faster. However, I rely on some Visual Studio addons, and addons are not supported in Express.
PS2: I have already closed all unnecessary windows. All diagnostic windows are on auto-hide. And all the tool bars are closed. I work almost completely using keyboard shortcuts.
Here are some tips, actually collected from following blog posts
###VS2008
Improve Visual Studio's Source View Performance
Tips to improve performance of visual studio IDE
Visual Studio 2008 Tweaks
###VS2010
Visual Studio 2010 Performance Part 1: Startup
Visual Studio 2010 Performance Part 2: Text Editor
Visual Studio 2010 Performance Part 3: A Technical Update
###Tips
Turn off background HTML validation.
Go to Tools / Options and select Text
Editor / HTML / Validation in the
tree view on the left side. Uncheck the Show Errors
check box.
Turn off AutoRecover. Go to Tools /
Options and select Environment /
AutoRecover in the tree view.
Uncheck the Save AutoRecover check box.
Close your property grid (View /
Properties Window)
web.config should not have <compilation batch=”false” />
Turn off AutoToolboxPopulate (Tools
-> Options -> Windows Forms Designer set AutoToolboxPopulate False)
Turn off Track Active item (Tools ->
Options -> Projects and Solutions
uncheck Track Active Item in Solution
Explorer)
Disable Navigation Bar(Tools ->
Options -> Text Editor -> C#, uncheck
Navigation bar)
Move file in App_Code into a class
library project
Disable validation Options for HTML
Editing (Tools -> Options ->
Validation -> Clear show error
checkbox)
I know that VS 2008 slowed down from VS 2005. I feel this pain every once in a while when im doing a quick Find or Find-Replace, or Find-In-Solution...etc. The UI sometimes isn't as fast as your hands are (when you're using keyboard shortcuts).
I found that just slowing down sometimes is the way to do it (it sucks, but then again, so does many things about Windows).
If it's load times youre concerned about; disable the startup stuff (from the Options menu). Here you can choose to load a blank screen upon VS load AND not to subscribe to any news feeds. (this helps alot depending on your internet connection).
you can also, via Options, adjust the visual animations that occur, as well as just disabling them altogether.
If there's anything else im missing, which im sure there is, i'd really like to know as well!
One thing that can potentially speed up visual studio is to disable document navigation.
Go to Tools -> Options -> Text Editor -> and uncheck 'Navigation Bar'.
This is definitately an option in 2008, pretty sure its in 2005 too.
Another option to try:
Go to Tools -> Options -> Text Editor and Uncheck 'Track Changes'.
Without knowing the information I posted in the comments I will say the typical stuff. Turn off all addons, if you are using vista or 7 switch to basic vs aero, check all running processes. This is where I would start.
For example, when I write:
string x = "turtle";
x.Go();
There is no red squiggly line detecting the absence of the Go() method on String.
Only when I compile does the error get detected.
I've just upgraded to Windows 7, I have Visual Studio 2008.
In my old environment the errors were detected before the actual compile.
Is there a setting that I am missing?
EDIT: "Tools -> Options -> Text Editor -> C# -> Underline errors in the editor" is checked.
I dont have the "Live Semantic" option. Maybe I need to go to SP1?
You need to turn on the underline errors in the editor and show live semantic errors options in Visual Studio.
These options can be found here:
Tools > Options > Text Editor > C# > Advanced > Editor Help
Edit: You will need to install SP1 for this functionality to work.
Select Tool -> Options, then Text Editor. Under the language you are using (ie C#), go to the Advanced and make sure the Underline errors in the editor and Show live semantic errors are checked
Stop the project.
Open Folder Project.
Delete .vs folder (he is a hidden folder)
Then restart Visual Studio
EDIT:
This approach has been around since the 2012 version of Visual Studio. This folder consists of keeping all breakpoint information and other settings saved. It is not known why, the configurations arrive at a time when the errors of compilations no longer appear. Deleting the .vs folder will "reset" your breakpoints forcing you to do them again if you need to.
For visual studio 2015 and higher:
Go to: Tools > Options > Text Editor > C# > Advanced > Editor Help
Then select: Enable Full solution analysis
I had the same issue and had SP1 installed and had Underline errors in the editor and Show live semantic errors checked in VS2008's options.
My solution was to download Microsoft Visual Studio 2008 Service Pack 1 (Installer) and re-install the package. It wasn't classified as a 'repair' or a 're-install' despite the fact it was already installed, but it worked.
Restarting VS solved my problem once.
my solution; I know it won't help like 80% of the viewers, but for the sake of who it will:
i have had a lot of noise in the IOS part of the solution, a VS bug that showed a lot of errors that weren't supposed to appear, so I just deleted the IOS part because I didn't really needed it as I didn't even had a Mac server to test it on... Something happened after that and the squiggly line returned! Seriously, VS team, fix your bugs...
JavaScript Type Checking
Sometimes type checking your JavaScript code can help you spot mistakes you might have not caught otherwise. You can run the TypeScript type checker against your existing JavaScript code by simply adding a // #ts-check comment to the top of your file.
// #ts-nocheck
let easy = true;
easy = 42;
Tip: You can also enable the checks workspace or application wide by adding "javascript.implicitProjectConfig.checkJs": true to your workspace or user settings and explicitly ignoring files or lines using // #ts-nocheck and // #ts-ignore. Check out the docs on JavaScript in VS Code to learn more.
In my case the problem was that I created a file with .s extension instead of .cs an then changed the extension to .cs once it was created.
I deleted it and created again correctly and now VS is underlining the errors in this file.
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?
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.
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.
Found it in Visual Studio 2019 as: Tools > Options > Text Editor > General > Show error squiggles
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
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.
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 Tools\Options\Projects and Solutions\General 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
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.
I had the same issue with 2017. There was a 'disable intelisense' option, make sure that is set to false.
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.
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
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.
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.