none
Trouble getting source server settings to work

    Question

  • I am trying to debug a small application on a workstation that I did not use to build the code. I have a step in my small build process to Index Sources and Publich Symbols (using the vNext build system). 

    The pdb file successfully uploads to the source server, and the pdb file is successfully loaded from the symbol cache directory I've specified in visual studio according to Debug -> Windows -> Modules.

    My application throws an exception deliberately so the debugger will have something to break into. When it does, I see the code that is throwing in the stack trace, so I know the symbols are loading correctly. When I double click on that entry in the stack trace, I am not taken to the source. 

    Due to the indexing information, I would have expected Visual Studio to get the source, but I am shown a file browse dialog. Note, I am using Visual Studio 2017.

    Here is the indexing information in the pdb file (which shows the pdb was indexed correctly):

    ------------------------------------------------
    VERSION=3
    INDEXVERSION=2
    VERCTRL=Team Foundation Server
    DATETIME=Thu Mar 08 15:58:40 2018
    INDEXER=TFSTB
    SRCSRV: variables ------------------------------------------
    TFS_EXTRACT_CMD=tf.exe view /version:%var4% /noprompt "$%var3%" /server:%fnvar%(%var2%) /console > %SRCSRVTRG%
    TFS_EXTRACT_TARGET=%targ%\%var2%%fnbksl%(%var3%)\%var4%\%fnfile%(%var5%)
    SRCSRVVERCTRL=tfs
    SRCSRVERRDESC=access
    SRCSRVERRVAR=var2
    VSTFSSERVER=REDACTED
    SRCSRVTRG=%TFS_EXTRACT_TARGET%
    SRCSRVCMD=%TFS_EXTRACT_CMD%
    SRCSRV: source files ---------------------------------------
    C:\Resources\agent\_work\6\s\REDACTED\AppDomainLogger.cs*VSTFSSERVER*/REDACTED/AppDomainLogger.cs*77776*AppDomainLogger.cs
    C:\Resources\agent\_work\6\s\REDACTED\CustomLogger.cs*VSTFSSERVER*/REDACTED/CustomLogger.cs*77776*CustomLogger.cs
    SRCSRV: end ------------------------------------------------

    Note, I  have REDACTED some information, it is just pathing information I don't want to reveal, and a server name, but they are correct. If the VSTSSERVER value and source code values are correct, why isn't the source code pulled up when I try to debug. I'm not sure what those numbers are in the source code paths, and I didn't see any login credentials to log into the tfs server. However, since I'm already connected to TFS by virture of using visual studio, I thought perhaps credentials aren't needed? My build process curently does not label source .... could that be part of the problem?

    I am a bit new at this (trying to use source information during debugging). Let me know if I'm missing something, and if I am, how I can remedy the situation.

    I DO have the Debug -> Options -> General -> Enable Source Server Support checked (and it's two sub-checkboxes) prior to attaching visual studio to the application. 
    Friday, March 9, 2018 1:42 AM

Answers

  • Hi BryanJohnson2,

    Just to make this issue clearly, could you debug your app without using the TFS? I mean that you could open your project using the VS IDE, and then debug your project directly in your side.

    Since the TFS forum was retired, for any TFS issues, you could post it to the Stack Overflow.

    In addition, as you use the TFS, you need to make sure that it has no build error with the TFS before you really debug your app, if it has the build error, you wouldn't debug it directly unless you resolved the build error firstly.

    Best Regards,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, March 12, 2018 8:08 AM

All replies

  • Hi BryanJohnson2,

    Just to make this issue clearly, could you debug your app without using the TFS? I mean that you could open your project using the VS IDE, and then debug your project directly in your side.

    Since the TFS forum was retired, for any TFS issues, you could post it to the Stack Overflow.

    In addition, as you use the TFS, you need to make sure that it has no build error with the TFS before you really debug your app, if it has the build error, you wouldn't debug it directly unless you resolved the build error firstly.

    Best Regards,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, March 12, 2018 8:08 AM
  • Hi,

    If I have the source that throws the exception on the same machine, I don't get prompted to browse to it. However, the point of the indexing information is so I don't have to. 

    I'll try stack overflow then.

    -Bryan

    Monday, March 12, 2018 5:07 PM