Rowupdating e newvalues is empty
If for some reason you need different text and/or translations for the same entry then you would have to consider a different approach. How would you add special values that may not be defined as part of the enum; am thinking of a Combo Box where the initial Selected Item might be something like "None" or "Select Gender" 3.
One possibility would be to modify the Resource Enum Converter. Any extra guidance for using this technique within an MVVM scenario?
If you use this as the datasource for a control then the Selected Value returned by the control will be a string - and you will have to somehow convert this back to the enum value which will be messy.From some googling it appears that, at least in the release candidate for NET2 this was a known bug; only binding to Data Sources lets those dictionaries be populated. | | From some googling it appears that, at least in the release candidate for NET2 this was a known bug; only binding to Data Sources | lets those dictionaries be populated. 2) I think it's weird that the "value" capability is tied to the parameters collection. That way it'd work with both types of data binding. I would like to confirm that this is a problem with the released version of NET2, so I can stop beating my head against the wall trying to get the Grid View to work "as advertised". As for the Grid View control doesn't correctly populate the Old Values or New Values parameters collection when performing udpdate operation, I think it is likely caused by some certain setting in the Grid View control... | | I would like to confirm that this is a problem with the released version of NET2, so I can stop beating my head against the wall | trying to get the Grid View to work "as advertised". - Mark Thanks for your followup Mark, Frankly speeking, I do agree with you that this is a big limitation since I haven't noticed this before until you mentioned this... What i simply did was to create a static method excepting IDBCommand. When I run the sample project and put a break point in the Convert To method the culture is correctly set to the Current Thread. Are you seeing this behaviour in the sample project or your own projectt? Thanks for the reply The first issue should not be a problem.