Could be a painful & bloody strategy too. :)
>That would be the "quick and dirty" strategy.
>
>
>>>And if you smack that designer hard enough the first time, they won't do it again.
>>>
>>>>If I define an method called OkButton_Click and attach it to the Ok button, and it's defined that way in the XAML file, then some designer who know zip about programming comes along and changes that name - he/she just broke the code. It won't compile.
>>
>>Is that a viable development strategy?
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people
