visual-studio-debugging

问题 It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 8 years ago . When I run my web application from Visual Studio I get the following message: Unable to connect to the configured development web server It then refuses to run. How do I resove this issue? 回答1: Please follow

问题 I was debugging a given C++ code with the F11 key (Step Into mode) in order to understand the precise order in which the functions in the code were called and I realized that it would never enter inside some functions unless I set a breakpoint at some line inside the function definition. I mean, if I call a function from the main method, and the function is defined in another .cpp I expect the F11 debugging mode to enter step by step inside the function in order to analize the variable

问题 Tools: Windows 7, Visual Studio 2010 and 2012, IE 9, ASP.NET 4.0, MVC4 Until a couple of days ago I had been able to debug by using the Script Documents section in the Solution Explorer. Now, the Scripts Documents section does not appear when Start Debugging (F5). I do have IE set as the default browser. Using "debugger;" has no effect. Configuration is set to "Active (Debug)." Silverlight debugging is off. I have 'repaired' the Visual Studio 2010 inatallation. I have no idea how to correct

问题 I'm using VS2010 Beta 2 to debug some multi-threaded code. Love parallel stacks, etc. I have a question, though: I have a breakpoint set in a method that may be called by multiple threads. Once I hit the breakpoint, I really want to keep the focus on the thread that triggered the that breakpoint. However, when I hit "step", VS often switches to another thread (say I'm stopped on thread 1, but in the meanwhile, thread 2 hits my breakpoint). I know that I can manually freeze threads in the

问题 In short: Console.WriteLine was working ok in VS 2015 but it is not working anymore in VS 2017. In detail: I have some VB code using Console.Write that outputs ok to Output Window in VS 2015, even when configured as Release ( to contrast with Debug ) launched with Start Debugging ( in contrast with Start Without Debugging ). Today I upgraded to VS 2017 ( Community version ), but the Console.Write is not working anymore in the same conditions as VS 2015. Maybe I made some config in VS 2015 in

问题 In VS2012, my web project debugs fine like always. I use IIS Express. Today, I installed VS 2013 and when I press F5 to debug, I get I can't find a solution to this anywhere. I tried clearing out temp files, change the port number from 7227 to something else, deleting iis express config files, etc. I even uninstalled and re installed VS 2013. I can run without debugging, then attach to IISExpress and that works, but I can't start with an F5. Any clues? EDIT: Happens on another machine as well

问题 Sometimes you don't really care about the name of a variable, because it does not go outside of your sub's scope. In fact, specifying the name would add an extra line of code. Also now you have this name to deal with, which may add to potential refactoring effort (if you decide to rename it later). Have a look at the code below: Dim fileInfo As New FileInfo("filename.txt") With New FileSystemWatcher .Path = fileInfo.DirectoryName .Filter = fileInfo.Name .EnableRaisingEvents = True AddHandler

问题 When running a console application in Visual Studio, depending on your settings, it will add a prompt after the program exits: Press any key to continue . . . I have found how to detect if I am running under the debugger(use Debugger.IsAttached ), but it isn't helpful. Press CTRL-F5 to Start Without Debugging sets this flag to false , yet still shows the prompt . I want to detect this because I'd like to display my own message and wait for a keypress, but not double up keypress checks . I don

问题 I have Visual Studio Professional 2013 and I am debugging an application which uses async/await extensively. But when I stop at breakpoint and open Debug/Windows/Tasks window, it always says "No tasks to display." I've made two test, in one I can see task, in another I can't (I run program, and pause it). Or I can breakpoint at waiting fro task line. using System; using System.Threading; using System.Threading.Tasks; namespace TasksDebugWindowTest { class Program { static void Main(string[]

问题 I was debugging in Visual Studio 2010, which we just installed and trying to look at a dictionary in the quick watch window. I see Keys and Values, but drilling into those shows the Count and Non-Public members, Non-Public members continues the trail and I never see the values in the dictionary. I can run test.Take(10) and see the values, but why should I have to do that. I don't have VS 2008 installed anymore to compare, but it seems that I could debug a dictionary much easier. Why is it