I\'m having difficulties with serveral of my VB.Net projects that I have upgraded to Visual Studio 2015. These projects have be upgraded over many years from visual studio 2003
FYI, I've just committed a fix for this that will ship in VS 2015 Update 2 (see https://github.com/dotnet/roslyn/commit/e683a8438d42d92a3d142ba53f38b33315c7dea2).
Another possible work-around for this issue in the meantime is to strong name sign your app (and the satellite assemblies). The debugger was correctly ignoring the multiple resource dlls in the strong name case but not in the "weak" name case.