In DevMode, the framework logs a number of extra warnings. In this case, a control is being submitted that doesn't have a corresponding property. This might be OK (and probably is), but in DevMode, the framework nags us just to be sure.
In production or late development, always set DevMode to false, since in DevMode the framework does a number of other similar things that can be helpful during development but are painful otherwise. I opened a ticket today to default our example applications to DevMode=false so as to alleviate some of the confusion. -Ted. On 2/28/07, Piero Sartini <[EMAIL PROTECTED]> wrote:
Am Mittwoch, 28. Februar 2007 schrieb Ted Husted: > Is DevMode set to false? no, its set to true.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
