I've tried following online instructions, but even though everything is unchecked and I save the changes, I am still getting word completion suggestions from IntelliSense. Any help would be greatly appreciated!
Related
When i'm typing code, the intellisense comes up to predict code, but before i can choose something in the list, its already gone. I know that you can use crtl+spacebar to bring it back up. But it's pretty annoying.
Does someone knows how to fix this?
(I'm using visual studio 17.3.1 (.Net - C#))
It is likely that this problem is caused by vs extension. You can try to disable the extensions and try again. If it doesn't work you can choose to reinstall Visual Studio.
I got Visual Studio 2015 Professional several months ago. One thing that has irked me ever since is how the syntax error checking fires off immediately after typing, whereas in 2013 the error checks only happened after you have moved away from your current line of code.
This is kind of difficult to explain what I mean. Essentially, if I type a quotation mark every single bit of code below that point immediately switches to string and everything highlights as errors. Halfway through creating a variable, Visual Studio is highlighting it saying it is an unused variable.
Is there a way to turn this feature off? I have been poring over every options menu I can find, disabling options one by one and I cannot find a solution. I have also googled ad nauseum and searched for a solution but it is either difficult to search for or nobody else minds. I find this feature highly annoying because the editor is screaming at me before I have even progressed halfway through a line of code.
Any help would be greatly appreciated
Rather than referring another website, I would suggest simple solution below:
Tools >> Options >> Text Editor >> General >> Show error squiggles
uncheck "Show error squiggles" checkbox
Ok, maybe this link can help you.
https://blogs.msdn.microsoft.com/zainnab/2010/05/01/how-to-turn-off-automatic-intellisense/
Also You can change colors for that error highlights (cheat your mind),
look for the error color and choose one equal to the back color of the editor.
https://msdn.microsoft.com/en-us/library/hh923906.aspx
I hope this can help you
I am new at FoxPro.
In a program I use, I do not see any intellisense in the editor.
Searched for it in the internet and saw that there is intellisense manager.
In my program it seems that intellisense is enabled.
One interesting point is that intellisense is working as desired in the command window.
But it is not working in the editor.
I tried Ctrl+J and Edit/List Members, still not working.
Do I skip something?
Mediocre VB.Net student here, but not a total noob. I've been getting this error: "The source file is different from when the module was built. Would you like the debugger to use it anyway?"
I chose Form1.vb on the "Find Source: Form1.vb" open file dialog box that followed. After that, my program has been acting very weirdly. For example, I have codes inside the sub that handles Button1 click, and then I moved those codes somewhere. Now when debugging, when I click that button, it executes the codes that I just removed a minute ago!
I'm scared because I don't to waste the 2 months of hard work that I've already spent on this project. Too friggin stupid to remember to backup the whole thing. Stackoverflow, please don't fail me now.
As you have explained i think the scenario is your modified code is not build correctly.. once rebuild the entire solution.
Please be sure work in debug mode, and then try Clean solution and then "Rebuild All".
refer following links may also help you..
the source file is different from when the module was built
Warning given when debugging source code in visual studio 2010
For some reason, I can't set a breakpoint in #functions when using Visual Studio 2013. Here's an example:
However, the same kind of breakpoint works in Visual Studio 2012:
If you move the #functions block up to the top of the razor page in VS2013 you can set a breakpoint in #functions once again.
You cannot set a breakpoint in #functions if the block is somewhere in the HTML.
Anyone know why? Maybe a bug? This is a big inconvenience if you're migrating an web app from MVC4 or earlier where #function blocks appear in the HTML.
This seems like a known issue. See reported bug in MS Connect.
Description:
"After my upgrade to VS 2013, I am no longer able to debug javascript within MVC razor files. "
http://connect.microsoft.com/VisualStudio/feedback/details/807088/unable-to-debug-javascript-from-the-vs-2013-ide-unable-to-set-breakpoint
I had all of the same issues with "This not a valid location for a breakpoint", and I also had no code highlighting or intellisense on any of the Razor code. None of the solutions I could find resolved it. Primarily because my issue was due to a really dumb oversight on my part, but just in case anyone finds themselves here and have made the same mistake, I thought I'd share it.
If you did not physically create the view yourself in Visual Studio, like if it was created with a NuGet package (Umbraco in my case), or if you opened an existing solution that isn't yours...The view may not be included in the project. You may see something like this
Notice that the Homepage.cshtml file is in there and I can edit it, compile it, render it etc. But I could not insert a breakpoint anywhere. Right clicking on the file and Selecting "Include In Project" was the fix for me.
What worked for me was Excluding the file then Including it again. Picked up the Breakpoints straight away.
Hope it helps!
What helped me overcome this issue was enabling the "ASP.NET" option in the project-properties. See the screenshot: