Update of Projects

I am implementing an UpdateProject method. If I do it similiar to the UpdateTasks method, that requires a DataSet to be passed back. Using this pattern, updating a project by sending the entire DataSet back could before _very_ expensive if you have a large number of projects.

Now, UpdateUser() takes a UserInformation object, but there is no analog for a Project. The closest I can come to is a DataSetProjectsRow object. Would it make sense to just pass back the row and not the entire DataSetProject?

I am not doing any bulk edits to Projects. This will be called once per Project, so there really isn;t a need for the entire DataSet to go back.

Mike or Scott, can you lend your opinion?

[696 byte] By [codefund.com] at [2008-2-20]
# 1
I have been implementing the same thing. I decided to*space
space*the editing of projects into two parts. Deleting a project, and editing a project name/desc. I created a manage projects form and implemented two new functions. Deleting a project by ProjectID was easy. NOTE I marked the project as Deleted no actual deletes. I'm trying to update a single project using ProjectID and I implemented an update proc using an executescalar. I keep trowing a SOAP Exception. Anyone else worked this out yet?
codefund.com at 2007-9-8 > top of Msdn Tech,Windows Forms,Windows Forms Sample Applications...