C# .net updates versus compile time debugging. How to stop the oddities?
Posted
by Fox Diller
on Stack Overflow
See other posts from Stack Overflow
or by Fox Diller
Published on 2010-06-05T23:25:51Z
Indexed on
2010/06/05
23:32 UTC
Read the original article
Hit count: 215
Are we reduced to ClickOnce to manage our application state for our users? We use Visual Patch currently. When our users update (we reproduced this) we get errors from the updated versions to our compiled versions. Since our developer state is not 'updated' with Visual Patch how can we monitor and eventual squash the various System.MethodNotFound, and System.NullReferenceException in our updated versions of our application?
© Stack Overflow or respective owner