Every time I'm going through an entire file searching of occurrences of a string, VS shows a poop-up notifying me about that. I've unchecked the option to continue that behavior at number of times - to no avail.
I went to options and unchecked it there as well (see image for verification) but every time I restart VS, the settings in back there - checked and unaffected. I'm out of ideas what to try to remedy it. (Googled it. I haven't found anything that I recognized as useful.)
Those settings are saved (when you close Visual Studio) in this registry key:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\Find
"ShowEndOfSearch"="1"
"ShowNoFound"="1"
"ShowAllReplacementsNotAllowed"="1"
"ShowSomeReplacementsNotAllowed"="1"
"ShowNoMore"="1"
"ShowFindStart"="1"
"ShowCancel"="1"
"ShowCancelBeforeReplacementsMade"="1"
"ShowReplaceInFilesWarning"="1"
Do you have access to that key? Try setting these values to "0" in regedit.
Related
I am trying to open a folder that I opened before, but it crashed.
I can open other projects, and restarting the computer didn't help.
Maybe it's because I had a big file opened (400mb) in this folder, but I cant close this file because the vscode crashing every time when I tried open the workspace..
https://github.com/microsoft/vscode/issues/126127
https://github.com/microsoft/vscode/issues/130375
I had the same problem.
Just delete the folders under %appdata%/code/backups/ and restart VS.
I solved the problem by restarting my computer and then opening VS code from a different folder.
To open large JSON files, I use Dadroit JSON Viewer, thus preventing the problem from repeating itself.
Not worry much about that!, same issue occurred in my pc but there is easy steps to fix this error as following.
solution: Enable "paging files" option OR increase virtual memory.
steps:
1). Right click on "ThisPC" or "MyPC" and go to properties. then go to "Advanced System setting". [ you can also find that using SEARCH button ]
2). then click on settings of Performance block. its open another pop-up window in that ,go to the "advanced" option .
3). you can see the Virtual memory section ,in that click on change button.
4). now first disable the checkbox of "Automatically manage paging file size for all drive".
-> and select the "custom size:"
-> in Initial size(MB): { you need to add the same value as recommended, which is also displayed downside section }
-> in Maximum size(MB): you need to enter the value that you get multiply by 3 of your allocated RAM size.
for example:
your pc's ram is 4 gb then you can enter 4098*3= "12288mb".
then set it , click ok, ok, ok, and then just RESTART your pc. 🥹
hope god will help you.
It's easy than you think, you just need to update your laptop. and try to use Vs code again you will see that it works.
How to avoid the window "No source available" while stepping into debug mode on VS2010 SL5
In Tools, Options, Debug, General Page. Check if you have 'Enable .NET Framework source stepping' enabled, if it is enabled, disable.
I tried all the suggested fixes; Nothing worked for me.
I finally figured out the solution after several hours of trial & error iterations.
It turns out that the 'No Source Available' error is due to a stack-overflow within the VS debugger env.
The C/C++ code function that was supposed to be stepped-into (by VS debugger), was using a variable that was initialized to a stack array of a few MB in size. When I replaced this with a heap allocation, VS was successfully able to step into the code.
This worked for me.
Please note that in my case, the actual code (with the stack allocation) ran without a stack-overflow error within the debugger (if I skip the No source available error). It was just that VS's debugger's was not able to step-into a particular function sitting inside another C/CPP file, because of the internal stack overflow.
Hope this helps.
You can hit Shift+F11 to step out and it will complete whatever unavailable function it is in and stop at the next line (it may be unavailable as well, but continue to use Step Out until you get to code you want to examine.)
Regarding VS2019, a description for the issue is provided at MSDocs.
For the requisite vcruntime and ucrt source files, the problem can occur after importing from a previous VS version which has since been uninstalled.
To prevent VS from using the old directories, find the solution property pages and navigate to the Debug Source Files Dialog Box.
Click the tick button to check the entries where any invalid ones can be removed.
The vcruntime and ucrt source should always exist in the directories, and the path at the top of the Browse to find source code dialog should always show the correct path.
In my case, because of a venerable drive bug, it is given to prompt for the "D" drive instead of the "C" drive. Further, the provided path cannot be pasted over to refresh the view, so, if none the wiser, one has to use the dialog to navigate all the way up to the required location from the desktop or equivalent.
Here there is an extension for this issue:
http://erwinmayer.com/labs/visual-studio-2010-extension-disable-no-source-available-tab/
But in my own experience before finding this article (I was in page but I was trying to fix it myself without reading article) I have fixed this problem just by accepting a confirmation message saying something like "Selected source file is different from compiled assembly. Are you sure you want to use this file for debug?". But I can't remember exactly what I did to get this message. I think there was a linklabel which I clicked on "No source available" window and then confirmation message appeared and after confirm the problem ran away.
I'm fighting with VS 2010 and this error that seems to be very common in previous versions, but it looks like not everyone is having it in the latest version.
I've got VS 2010 SP1 and I'm getting this error quite often.
The problem is that it's not even enough to restart VS in order to make it go away, I usually have to restart my PC, and I'm losing a lot of time doing this (it's quite frequent)
I've got Windows 7 32bits (can't upgrade to 64 bits, the company doesn't allow it), and I can't do things like creating another solution (please don't reply this :) )
I've used the command to make devenv.exe LARGEADDRESSAWARE, but the error keeps on happening.
My virtual memory size is set to automatic, and the weird thing is that VS doesn't even take 2GB of ram, so I don't know if the error is really because it's lacking memory, or if it's some bug in the program
Any ideas, things to try, something?
I tried everything else as well. The problems continued to come back until I tried
http://blog.rongabriel.com/2010/03/08/not-enough-storage-is-available-to-process-this-command/
Edit: Link is dead, archived version: http://web.archive.org/web/20100929160038/http://blog.rongabriel.com/2010/03/08/not-enough-storage-is-available-to-process-this-command/
Click on Start > Run > regedit & press Enter
Find this key name HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters
Locate IRPStackSize
If this value does not exist Righ Click on Parameters key and Click on New > Dword Value and type in IRPStackSize under the name.
The name of the value must be exactly (combination of uppercase and lowercase letters) the same as what I have above.
Right Click on the IRPStackSize and click on Modify
Select Decimal enter a value higher than 15(Maximum Value is 50 decimal) and Click Ok
You can close the registry editor and restart your computer.
This can be found under MS KB https://support.microsoft.com/en-us/kb/285089
Have a look at
Visual Studio 2010 -- how to reduce its memory footprint
I think I got the best results when I turned off C++ headers index. YMMV
Check the output project type in properties. In my case it was changed to "Windows Application" though it was a "Console Application".
Switching back to console application solved my problem.
I had downloaded and installed VS 2010 Ultimate evaluation for 30 days. It allows me to get a 60-day extension if I register. My register just ended.
2 days ago, I got the extension key by registering but did not enter it because I thought I should wait till the product evaluation period expires.
Now, when I open up VS 2010, it gives me a dialog box with only two buttons:
a) Learn more about upgrading. This takes me to the same page that allows me either to buy or generate an extension key.
b) Close. This closes VS 2010.
How do I enter in the extension key now?
In order to update the product key you need to be logged on with administrator privileges. Try logging on as an admin and the go to the control panel > uninstall/change a program > Enter the product key > click "upgrade."
Here is a link from MSDN on how to do it for VS 2008 trial editions. It is the same for VS 2010:
http://msdn.microsoft.com/en-us/library/cc442563(v=vs.90).aspx
I did the same exact thing and it looks like the only option I could find after tons of googling is redownloading and installing the latest version to use your new key with. Here is the page I found with links to the downloads:
http://msdn.microsoft.com/en-us/vstudio/bb984878.aspx
NOTE: I have not yet downloaded this and tried the key I received from the 60 day extension but will let you know if this works when I get a chance to DL it in the next couple days unless anyone else can confirm.
(Probably too late, but here's an idea that may help someone...)
Try setting your computer's date back to a point in time when your trial was valid (e.g. 1 month ago). I've just tried this on an expired 2010RC and it ran happily, allowing access to the Help>Register menu option.
Of course, attempting to register in this way may detect that you're running "in the past" and refuse (at which point, try setting the clock back and see if it'll let you retry) - but it's worth a try before going through the pain of reinstalling the whole thing from scratch.
Try "Help -> Register Product". It can be your answer
I've successfully made several Visual Studio debugger visualizers, and they're working very well, except that on some objects I get a time out error when I try to deserialize the object with objectProvider.GetObject()
System.Exception: Function evaluation timed out.
at Microsoft.VisualStudio.DebuggerVisualizers.DebugViewerShim.PrivateCallback.MaybeDeserializeAndThrowException(Byte[] data)
The time out happens rather quickly (maybe about a second after I click on the visualizer icon), even though some of my other visualizers work fine even with large data objects that much longer to display (5-10 seconds) and still don't timeout.
I've already made a custom object source to limit the serialization to the fields I need to display. What else can I do to get the data to deserialize without timing out?
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Debugger
I think this is not documented, but you can try changing some of the Timeouts in the above registry key, and restart Visual Studio.
I was recently hit by this in VS2012 and after googling I found this:
As the exception message says, this exception means the debugger
visualizer for the datatable is timed out. In VS debugger, each
expression evaluation windows(such as watch window, locals window,
datatips, autos window etc..) has different default max expression
evaluation timed out value. For datatip, we prefer to give a short
time out value because otherwise it will provide a poor user
expression. If you do want to use the visualizer functionality for
that datatable, you may add the expression to a watch and try to
visualize it.(Because watch window has a longer timeout value). If you
do want to get rid of this timeout in datatip, you may try to increase
the timeout value for datatip. The timeout value is a setting in
"DataTipTimeout" registry key under:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\Debugger Note:
you should probe WOW64Node for 64bit OS. You can also see other
windows' default timeout value under this key.
To Visual Studio debugger work well - "Locals" window in "WPF visualizer" (tested in WPF application), you need to find in registry:
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\Debugger\
DWORD parameter "LocalsTimeout" and default value (1000) set to big enough value, 5000, for example.