For this to work simply add the remote folder path to your symbols location list.
To use the new debugging solution to debug a remote. pdb files, that then can be picked up by VS when remote debugging. You can, however, continue to use the old-style procedures and debugger just as they are described here. This allows me to programmatically create and deploy a MSI which can include. Due to this limitation I switched most setup projects from ClickOnce to Wix#. I checked the setup and Individual Components, and its not listed there either. As soon as the project is an Office AddIn, the option to specify the files you want deployed is gone. I cant find the Remote Debugging tools for Visual Studio 2017. pdb files but only if the application to deploy is not an Office AddIn.
The symbol files for mixed (managed and native) applications must be located on both the Visual Studio host computer and the remote computer.Īpart from that, I've noticed that a ClickOnce application can provide the. The symbol files for managed applications must be located on the remote computer. The symbol files for native applications must be located on the Visual Studio host computer. Here is a brief excerpt from MSDN about this: Turns out there are a few cases where you need the PDB files both on the remote host and on the client.
When I tried to remote debug a windows service I was wondering why VisualStudio kept telling me that my BreakPoints wouldn't be hit because the symbols haven't been loaded, although the PDB files where on the remote host. Visual Studio Remote Debugger and PDB files - Published 18 Jan by MemphiZ.