Never ever change snk files during development
assembly 1 is signed with snk 1 . alot of apps are using assembly 1. a developer for some reasons created a new snk file and resigned the assembly and redeployed it. i know that all of us know that all apps will not work. but this really happens alot with developers. i faced it alot with my developers in the last month so i decided to write about it.
snk is not a configuration that we can change . think about it like a critical change where all the behaviours of the application will change.