Mass compile should be able to help with different assembly versions

[JonP]

When installing a bunch of VIs at a customer site we often get problems that they need to be recompiled, not because the LabVIEW version is different but because third party DLLs that the VIs might be dependent on have a slightly different version number. It seems that mass compile is perfectly capable of detecting this problem because you get errors like:

- Expected Assembly "<AssemblyName>, Version=1.0.0.10, Culture=neutral, PublicKeyToken=null", but found "<AssemblyName>, Version=1.0.0.11, Culture=neutral, PublicKeyToken=null."

but sadly the VI does not get recompiled. So you have to manually open every affected VI (which does not load broken because APIs are almost always backwards compatible but it has the changed asterisk) and save it. Is there any way to force mass compile to recompile such VIs?

[JonP]

I hereby withdraw this question (there doesn't seem to be a way to delete it). The affected VIs do get recompiled, it was just a permissions problem.

[billko]

Don't forget to give yourself a pat on the back - i.e., mark your last post as the solution!

[JonP]

I can't! Possibly because I "muted" the post, whatever that does, and i can't unmute it.