Runtime binding: a peculiarity
Today I noticed that if I changed my solution so that the runtime exe sees a different file as the primary file (different than it did in prior version of the runtime solution), I could not just sent the user a new exe file along with the runtime solution files. Eventhough the new exe file was bound with the same binding key, it still attempted to load the file that used to be the primary file.
With patient exploration, I found that one particular Windows file, found in the Extensions\English folder, must be replaced:
If that read-only file isn't updated with the one created when the new runtime is created, the exe file attempts to load the file that used to be the primary file, not the file that's bound as the primary file to the new exe file.
Does this make sense? It makes me think, I might have to send the user the entire complement of Windows runtime support files with the new runtime exe and solution files, just to play it safle, as long has I have changed what the primary file is.