That failure doesn't make sense to me. . .

I understand it's a linker error, but I don't see how that error would be appearing from this change - unless the dependencies aren't being built in the right order? But then why would it work locally and not here?

Were you clean building locally? I would expect that is the only way to test for sure.

This warning is suspicious, because all of the unresolved methods are in that file:

x64\Release\typeresolution.obj : warning LNK4042: object specified more than once; extras ignored

It makes me think that the multiprocessor build is processing this file twice and one of them is not so good.