Mdb automatic generation bug?

Unity Engine
1

Hello,

I’m working with unity 5.5, visual studio 2015, and vstu 3.1, on a project with external dlls that are copied into assets/plugins folder.

It seems from unity 5(.X?) that mdbs are generated automatically on import in unity (perhaps due to vstu installation?).
But sometimes they are not, and I can’t understand why.
It seems if dll and pdb have changed with an identical code source mdbs are not regenerated, but I’m not sure.

When this happens it’s no more possible to debug in visual studio.

I can use pdb2mdb (this one pdb2mdb for Visual Studio 2015 · GitHub) to manually generate it (it fixes the problem), but I would prefer to understand on what condition unity choose to regenerate this mdb.

Do you know how it works?

2

Me too, have met this problem.
The issue is that, as the path of Unity Engine is not the same for everyone in team and not in project path, it’s not possible to use macro or something to reproduce the auto process.

3

Also encountered this issue a while ago, had a hack to bypass the issue but it is no longer viable.
In case any person stumbles upon this issue and wants to vote for it to be fixed, here is the entry in Unity’s public issue tracker.