Net detailsview itemupdating
Scott I have to say I've had just about enough of this wizard-driven all-your-code-in-one-place orientation you find everywhere in the documentation and samples. Main idea is that after the state is changed you have to rebind your control to make it actually "see" the changes.the above snippet should be changed like this: Just wanted to add my two cent for those still having this problem.NET: You will now have a detailsview which shows 2 rows, one for Name and the other for Publisher.If you click Edit, you will have to click it twice to get into edit mode, then twice to cancel out.on the modechanging event ensure that you do the data Bind() last after you have set the change Mode or it will not take effect and will require the edit button to be pressed twice.
Jono One thing i didn't mention is that I didn't set the Data Source on the Details View in the aspx page.I have to click Edit and Cancel twice for them to do their action.The first and second click are calling the Mode Changing method so I assume there is something wrong with my code and the same with just B's code.If I don't put in the Mode Changing event implementation I get an exception: "The Details View 'dvw Work Item' fired event Mode Changing which wasn't handled." I do intend on adding other custom code into this method because certain actions need to happen when you start editing or inserting.Here is the code I have so far: How did you use a repeater instead of a Details View, that would be strange because each now is the next field instead of a row like the Grid View.