TFS built dlls fundamentally different?

[NewsBot]

So we have a system, wherein dlls built by team system server (2005 I believe, although we have little to no access so I have no idea the exact version and patch setup.) are used in a different visual studio project.

 

Except recently, replacing the old dlls with the new has led to the new dlls not being recognized. (Previously the old references would be fine, and reloading the project would show any code changes or new types.) Now the references are all broken (marked by the yellow warning symbol. Reloading the reference seems to fix them, but there are a heck of a lot, and builds seem to go wonky now claiming "no public types".

 

Reflector and ildasm both show very little different between dlls built locally and on the server, except local dlls work (and are twice the physical size) whereas the server-built dlls don't.

 

Anyone got a clue as to what's going on?

 

More...

 

View All Our Microsoft Related Feeds