根据微软的说法，没有办法用托管代码可靠地实现这一点。这是他们意识到并正在努力解决的问题:

For those out there who have experience debugging native C++ or VB6 code, you may have used a feature where function return values are provided for you in the Autos window. Unfortunately, this functionality does not exist for managed code. While you can work around this issue by assigning the return values to a local variable, this is not as convenient because it requires modifying your code. In managed code, it’s a lot trickier to determine what the return value of a function you’ve stepped over. We realized that we couldn’t do the right thing consistently here and so we removed the feature rather than give you incorrect results in the debugger. However, we want to bring this back for you and our CLR and Debugger teams are looking at a number potential solutions to this problem. Unfortunately this is will not be part of Visual Studio 11.

https://connect.microsoft.com/VisualStudio/feedback/details/597933/add-a-return-pseudo-variable-to-the-visual-studio-debugger-for-net-code

在VS2019中，只需打开调试->Windows->汽车窗口。在那里，你看到concat返回值如下所示:

我想在Visual Studio 2015中扩展PascalK的答案，因为有一个隐藏的特性没有在检查方法调用的返回值中记录。

如果有嵌套函数调用，则会自动创建伪变量$ResultValueX，其中X指的是函数调用顺序。因此，如果你有一个像Multiply(Five()， Six())这样的调用，则会创建以下伪变量:

Five()     | $ResultValue1 = 5
Six()      | $ResultValue2 = 6
Multiply() | $ResultValue3 = 30

使用Shift-F11走出go()方法，然后在“Autos”调试窗口中，它将显示方法调用的返回值，该方法调用刚刚弹出堆栈(在这种情况下，go()方法是你想要的)。这是Visual Studio 2005中的行为;我还没有使用Visual Studio 2008，所以我不知道这个行为是否在那个版本相同。

是的，通过切换到VB.NET。P)你刚才说了“Visual Studio”。,)

在我的记忆中(从Visual Basic到VB.NET的所有版本)，您可以简单地查询函数名。它像一个局部变量一样“起作用”，在函数开始时隐式声明，它的当前值也被用作函数通过非返回语句退出时的返回值(即Exit function或只是falling through)，当然，当使用return语句时。

它还被设置为return语句的表达式。就像局部变量一样，它的值可以在函数内部的任何执行点检查(包括在return语句执行之后)。c#没有，也应该有。

That little VB.NET feature (plus the Exit Function statement which it enables - another feature C# doesn't have and should) is very useful in a form of defensive programming I practice where I always initialize the function name to the failure/default value as the first statement. Then, at any failure point (which normally occurs much more often than success points), I can simply call the Exit Function statement (i.e. without having to duplicate the failure / default expression or even a constant/variable name).

您可以尝试选择“someTableAdapter.getSomeData();”，右键单击它，然后选择快速观察。