Viewing function return values in the Visual Studio 2013 debugger

Viewing function return values in the Visual Studio 2013 debugger

Rate This
  • Comments 4

One of the great new features in Visual Studio 2013 is the ability to view function return values in the debugger.  This works not just for C# and VB, but for F#, as well.  We didn’t include this in our list of new Visual F# tools features for F# 3.1, but we think it will make many F# developers happy nonetheless!

 

debugger

 

It even works for curried and anonymous functions, if you step through the code.

debugger2

Leave a Comment
  • Please add 5 and 1 and type the answer here:
  • Post
  • This is the one of most basic debugger features one could imagine, looking at return values -- I wish it had appeared years ago, but kudos!  

    For F#, what would be nice is a "run to next pipe and inspect value" so that I could go though each |> and look at the values along the chain.  I know the pipe is just syntactic sugar for re-ordered function application, but its use is so pervasive that would be nice if it were treated as it's own debugging boundary. (I've overloaded |> myself w/console output, but that gets ugly fast.)

    In the more general case, if we had pragmas or meta-data that defined custom, named debugger boundaries, then the compiler (or a plug-in writer, etc.) could add these for |>'s or wherever else, end then custom toolbar items would automatically be added to the debugger in VS for each active custom boundary - so you'd have a "Pipeline" group with "Step In", "Step Out", "Step Over", "Run to this", etc., items for that boundary. So the current "Function" group becomes a special-case of the more general debugger boundary support.

  • hello, I opened http://www.tryfsharp.org/ in Internet Explorer 11 on Windows 8.1.

    I get the following error:

    "Welcome to Try F#! Your system does not support the execution of F# code in the browser.

    You can still read the tutorials and view code in the editor. Please see the Explore section for other ways to run F# code."

    Can you please fix it for future versions of Internet Explorer.

  • hi This is the one of most basic debugger features one could imagine, looking at return values -- I wish it had appeared years ago, but kudos!  

  • patty: use "Desktop IE", or Firefox.

Page 1 of 1 (4 items)