Are we reduced to ClickOnce to manage our application state for our users?
We use our own installer and Visual Patch currently. When our users update using our Visual Patch download (we can reproduce this) we get errors from the updated versions which never show up in our dev enviroment.
Since our developer state is not 'updated' with Visual Patch how can we monitor and eventually squash the various System.MethodNotFound, and System.NullReferenceException in our updated versions of our application?