Add assembly version and "integrity" check

[SubPointSupport]

SPMeta2 should check versions of its libraries used.

The problem is that sometimes various SPMeta2 assemblies are used:

• from the local folder
• from GAC

Such inconsistency might and does lead to heavy issues with serialization/deserialization, provision and other funky stuff - CSOM assemblies might be older but debug/trace logs would say that SPMeta2 is up to data.

There should be a new service which would check version of SPMeta2 libraries used - all of them should be the same version across the board.

Based of several feedbacks including the following: https://www.yammer.com/spmeta2feedback/#/Threads/show?threadId=943016920

[andreasblueher]

I've ran into this issue myself before!

[avishnyakov]

@andreasblueher, what was the scenario on which you had this issue?

[andreasblueher]

I had used a different version for building my solution than the one which was deployed to the server. Not sure if there's something you can do about that, but since I know I haven't had this issue again.

[avishnyakov]

Same-same here, either WSP deployment or desktop/console app would fail due to assembly mismatch. Rare, but extremely hard to troubleshoot situations. We'll add this check to avoid this consufion and keep everyone sane.