Debugging in Visual Studio opens the wrong source instead of the file on the symbol server (if the source files have the same name)

I've searched far and wide for a solution to this but can't find one.

I have configured TeamCity to publish packages with both the symbols and source in them to ProGet. This process works great and ProGet correctly identifies the symbols.

I have setup Visual Studio as per the instructions on ProGet's knowledge base i.e.

• Adding the symbol locations in options->Debugging->Symbols
• Enabled source server support options->Debugging->general

I've checked in Fiddler and the symbols are downloaded when I launch our app in debug.

Then when stepping in to one of the methods in our package it opens the wrong file. The file it opens is however named the same (we have a file called Component in each of our packages and also in local solution that pulls in the package).

If I change the name of the file and re-package and publish it to ProGet the problem goes away and I can step in to file during debugging but this seems like a hack.

Does anyone know how you can get Visual Studio to favour the file on the symbol server over any local files in the solution with the same name?

Symbol files in the project directory are always loaded, for this issue, a sample could help us understand the symbols loaded easily. If your local cache folder had the symbols file which was downloaded from the Symbol Server before, I know that it would not download it again during you debug your app. So my understanding is that since your symbol file has the same name, the VS debugging would search and load the symbol from your local project folder firstly, and then download it from the symbol server or others if your local machine has no them. That's the reason why you got this issue.

The workarounds I could think of:

(1) Load the symbols manually from Debug modules windows if you really want to use two files with the same name.

(2) Using different names would be better.