I just stumbled over the same issue and figured out that my fault was the existance of two versions of that assembly within my probing paths. That typically happens if you first did your assembly and afterwards fix a postbuild event to move it to where you really need it.