In a team project I\'m working on, setting a breakpoint in a file (say IdeasController.cs
) will lead to erratic debugger behaviour if there\'s another file with
I had a very similar problem. In my case the problem was a different target .net framework in one of the projects causing VS2017 to wrongly load a source file (with the same name) of another project, not the one being activated with
ObjectHandle handle = Activator.CreateInstance
Changing the project's target framework to be the same in all projects fixed it.