To be clear, my only goal was to support the new data binding in ASP.NET 2.0, not to build a complete replacement for data binding that would move data into/out of arbitrary controls on a web page. If that is your expectation then it will probably always be "incomplete", because that's not its purpose in my mind.
It is, of course, possible to use data binding and templated fields at the same time - I do this in the PTWeb project. In that case the data binding infrastructure does provide those values and so DataMapper is able to use them. If you look at DataMapper, it is not complex, nor is it intended to be complex. It really is just a mapper from one object into another.
I guess what I'm saying, in short, is that web technologies remain quite immature in some ways, and I view this whole thing as a limitation of data binding in the web more than anything else.
Rocky,
Thank you for clarifying the capabilities. I think what would be helpful for the community is to provide some "best practices" for how we should map data from controls into their associated object properties. For example, I mentioned in my last post that I was using .FindControlById("id") and then accessing the public property of the object with the control value. Just wondering if there might be a better way to move those values into the object.
Copyright (c) Marimer LLC