Why are no Symbols loaded when remote debugging?
Make sure you copy the .PDB file that is generated with your assembly into the same folder on the remote machine. This will allow the debugger to pickup the debug symbols.
Make sure you copy the .PDB file that is generated with your assembly into the same folder on the remote machine. This will allow the debugger to pickup the debug symbols.
Ctrl+- should do the trick which is the standard keyboard shortcut for Navigate Backwards. Or using the navigation buttons in the standard toolbar. This is explained on MSDN at https://blogs.msdn.microsoft.com/zainnab/2010/03/01/navigate-backward-and-navigate-forward/ On this MSDN page, you can see the following explanations The editor remembers locations when you move in a single command more than several lines … Read more
Debug -> Windows -> Call Stack (Ctrl + Alt + C is default bindings (I think)) Will show you the history of execution, you can double click events to go to definition, however you cannot step back in code But you can drag your little yellow arrow to another point in the code to re-execute … Read more
Ray is correct when he says that Visual Studio’s default format for text is something like UTF-8. Although Notepad++ is a great tool and I use it myself, there is an alternative in that you can tell Visual Studio to store your text file in ASCII format: In VS2008, select your file in the solution … Read more
Check in all pending changes within the folder and ensure that all other team members to do the same. Ensure that you have a copy of the folder in your working directory (otherwise, you will not have the option to rename the folder in the Source Control Explorer in the next step). Get latest version … Read more
Try do the following (working in all Visual Studio versions from 2012-onwards): Tools -> Options -> Source Control -> Visual Studio Team Foundation Server -> Uncheck “Attempt to automatically resolve conflicts when they are generated”:
Go to Tools → Options → Text Editor → C# → Advanced, check the following options: Underline errors in the editor Show live semantic errors
Check this setting: Tools > Options > Windows Forms Designer > General : AutoToolboxPopulate It should be set to True for this to work.
If you use ReSharper, you can enable it by going to ReSharper / Options / External Sources, and move up “Sources from symbol files”. Then in the tab “Sources from symbol files”, click “Advanced” and there you can map source folders.
Deinstall the .NET Framework xxx Language Pack. (xxx = boring message language)