Is there any way to find which DLLs are being accessed via reflection in .Net application?

I am working on a .Net solution that contains 270 C# projects. They all have a physical reference to each other. But there are some projects which they refrenced each other without any useing/call. For example, project A added project B as a reference but when I remove this reference from the project A and hit the build button all goes well with no Error. But this still does not tell me that I can safely remove the reference to the project B because there might be some codes that are accessing the project B methods via reflection. Now rescale this example to 270 projects!! Is any tool or solution to find out this kind of dynamic dependencies without going through the line by line of code? I know ReSharper and VS 2017 shows you unused dlls but I am not sure if they consider this corner case as well. (call a dll via reflection)