I noticed a strange issue today with Visual Studio (2010,2012,2013). Some of the modules are missing, not just symbols, but they are not present at all in the Modules window. When I check the count that VC is showing - exactly 500... Is it really possible, VC has a limit and it's so low?
I came across this exact issue today. Visual studios has a hard limit of 500 modules. I am not sure of the reason. Here they describe a way to raise the limit by adding a registry key.
Add this key to your registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
DWORD DebuggerMaxModuleMsgs = 2048
Related
I've updated Visual Studio several times since release but occasionally it seems to act like it's creating a duplicate (as you would with a duplicate file/folder) and post-fixing a number to it e.g. Visual Studio Professional 2022 (3)
Anyone know how to fix or correct this? I've gone through the start menu, short cuts, etc. which also had the duplicate indicator but they were the only entries in their respective locations. I corrected the name which fixes it in Windows itself but the Installer still has the (3) in it.
While updating or uninstalling Visual Studio Installer Projects Extension Preview the step "Microsoft Visual Studio Preparation" is taking enormous amount of time. I may say it gets stuck.
My suspicion is the installer (Windows one, not the extension itself, since it is getting modified--updated or uninstalled) is making changes to the registry.
VS registry entries are too many to investigate them one by one. Re-installing VS is not an option. (I have VS 2013 Ultimate on Windows 8.1.)
So, my question is: is there any tool to repair, optimize, clean, or otherwise modify registry (VS portions only) to get the process quicker? Or some sensitive keys that need to be explored? Seems like there are timeouts involved? (Although I do not find this quite reasonable...)
Or, if I am wrong about the registry, Is there another reason for this symptomatic behaviour? UAC issues? NTFS security? Other?
Any advice?
Thanks.
I just solved a similar issue with installing Visual Studio 2013 Update 3. It was taking over an hour on the "Microsoft Visual Studio Preparation" step.
I fired up Process Monitor from Sysinternals and realised the installer was busy logging to C:\FusionLog. Killed the update process, changed the relevant settings under HKLM\Software\Microsoft\Fusion to turn off assembly bind logging, rebooted to make sure the new settings were recognised, and voila, the "Microsoft Visual Studio Preparation" step took on the order of 10's of seconds.
I hope this helps with your problem because this was extremely frustrating for me. I wasted most of my work day on this.
When "Microsoft Visual Studio Preparation" is shown, the installer is running "devenv /setup" to register any packages and templates. That can take a long time. Though it's not ideal, it's not a bug; it's how Visual Studio works.
See this blog posting: http://blogs.msdn.com/b/heaths/archive/2014/01/21/upgrading-visual-studio-2013-update-to-a-newer-update-may-be-slow.aspx
It basically says there's no workaround to save time, just sit tight:
"There is no current workaround that will save time. You might consider starting the upgrade before taking a lunch or heading out for the day."
It also says the issue has been resolved for future versions of VSUpdate and Visual Studio.
Try to block the antivir activity. As for me, it significantly raised the speed.
My Visual Studio 2010 was working fine this morning (I run in in XP sP3 under Paralles) I restarted the entire laptop and I started getting this error. I even uninstalled VS2010, deleted the Visual Studio 20010 directory on the My Documents area and reinstalled it, and it is still giving me that error every time I try to start it.
I'm not sure if stackoverflow is the place to ask it, but I am at my wits end trying to get this running again (trying to avoid rebuilding the entire Virtual PC) Does anyone know how to fix this?
Not sure how this is caused, but possibly related to having multiple monitors - I have been alternating between running 1 or 2 monitors. Found a solution here:
http://rainabba.blogspot.com/2010/07/visual-studio-2010-wont-start-120-is.html
Basically, the erroneous negative width value(s) are stored in the registry, not on disk, so try this solution before the other destructive solutions in this SO question.
Fire up regedit, and navigate to:
HKCU\Software\Microsoft\VisualStudio\10.0\MainWindow
Edit the registry value, replacing any negative numbers with positive numbers (I replaced two instances of '-1' with '200')
Starting with Visual Studio 2017, settings are now stored in a private registry hive. You will need to first load the VS2017 registry hive:
Select HKEY_USER in regedit.exe
File -> Load Hive
Browse to %LOCALAPPDATA%\Microsoft\VisualStudio\15.0_{INSTANCE}
Select privateregistry.bin and click open
Give the loaded hive a name such as VS2017
Once the hive is loaded, locate the MainWindow value and fix the negative value in it.
The private hive can only be used by one application, so you will now need to select the hive you just loaded and unload it with File -> Unload
As for locating which instance is the default instance, I just looked for the most recently update file.
This solution of changing any negative values to a positive value in the MainWindow registry entry also works for Microsoft SQL Server Management Studio - tested on v13.0.
HKEY_CURRENT_USER\Software\Microsoft\SQL Server Management Studio\13.0\ MainWindow
I ran in the same trouble with Visual Studio 2013.
I've tried the methods described in the other answers, but the one that worked was modifying in the registers. It seems the Registers have changed since VS 2010.
For VS 2013, you have to modify
HKEY_USERS\S-1-5-21-1181729300-1976498228-1094237608-1001\Software\Microsoft\VisualStudio\12.0\MainWindow
Just make sure there's no negative value. I replaced -580 with 100.
Good luck!
regedit fixed the problem...searched for the invalid width number under the microsoft key...(found key=MainWindow). Edited the value and removed the 'negative' character.
Try deleting files under <username>\Documents\Visual Studio 2010\Settings. That's where your user preferences are stored, including (I think) which windows you placed where. These are not deleted when you uninstall or reinstall VS, so if something is botched in there it will still be botched after a reinstall. Also look for droppings under <username>\AppData\Local\Microsoft\VisualStudio\10.0.
Do you see anything in the application event log?
Try these
devenv /ResetSettings
devenv /installvstemplates
Delete contents in here:
%ProgramFiles%\Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplatesCache
Seeing an issue when debugging in Visual Studio. All of the values under watch, and in the hover over window show up incorrectly. the only values that show properly, are values that are local to the method I am currently stepping through.
For example the watch value for 'this' when debugging shows the following under value
0x00000000ffac0388 { btnBack=0x00000000ffaccf20 btnReply=0x00000000ffacd200 btnForward=0x00000000ffacd420...}
some other variables show this, even though the variable is there.
error: 'this.foo' does not exist
The machine recently had windows 7 64 installed, since then this problem has occured.
Visual studio has been reinstalled on this machine, and we verified that the settings in visual studio were exactly the same as a different PC that is the same machine and config.
We finally figured out what the issue was. The devenv.exe was being set to run in xp compatibility mode (sp3). Doing a rebuild of the project after removing the compatibility mode fixed the issue.
Can you provide a bit more information to help us track down this problem. In particular
What operating system was installed before upgrading to Windows 7 64 bit?
Did you install Visual Studio before or after the upgrade?
Is there any other version of Visual Studio installed on the machine?
If you set your application to be x86 specific does the problem still repro?
What language is your code written in (assuming C#)?
When facing weird debugging issues, I find that deleting the solutions User Options file (.suo) usually fixes the problem. You will loose your bookmarks, breakpoints, any special exception handling, and so on.
If that fails then clear all your Visual Studio "temporary" files. Check out the "Clear Recent" script at http://missico.spaces.live.com/blog/cns!7178D2C79BA0A7E3!370.entry. Modify it for your own needs. For instance, I dislike Flash, so you may want to remove the call to ClearStupidFlash and the other non-Visual Studio calls. Clear your solution then "rebuild all".
If the problem still exists, then something else is going on.
A couple of months ago, the MRU list in Visual Studio stopped working. Neither the File menu or the start page shows any recently opened projects or solutions. I honestly have no clue what I did to cause this, but perhaps someone who knows more about the murky depths of VS might be able to hazard a guess at what caused it to disappear, and even better, how to get it back?
It is a pretty normal VS2k8 Team System installation with SP1, running on a 32-bit XP SP3 machine.
Edit:
The registry key HKCU\Software\Microsoft\VisualStudio\9.0\ProjectMRUList exists, but is empty.
Permissions for that registry key seem pretty normal. The user I'm running VS as has both read and write access to it (and has admin privileges in general).
You might run RegMon / FileMon (ProcessMon) from SysInternals as to ensure it is access the correct path, and that there are not permissions problems, etc
Forgive me if you've already checked the obvious: there's a setting under Tools, Options, Environment, General, where you can set the # of items to be displayed in MRU lists. Is it possible that somehow this has gotten set to zero?
Try out Recently Used Files (supported for 2010,2012 and 2013) that maintains an MRU list on a per-project basis.
Visual Studio 2012, 2013: http://visualstudiogallery.msdn.microsoft.com/a61cbd1d-b5a2-490b-a6bb-f0ea3ecf214a
Visual Studio 2010: http://visualstudiogallery.msdn.microsoft.com/45283881-5a62-4dc1-8ffb-4cbc02709947
Its free, and very efficiently manages the MRU lists for your projects.