Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Just doing some work with RIA services and I see in the MSDN documentation that neither it or any parents up its’ hierarchy implement IDisposable. I’m wondering what the design decision was for this…as DomainContext is a stateful resource, wouldn’t it be nice to have a Dispose() to release it when done ?
Thanks,
Scott
A stateful object doesn’t imply IDisposable is required.
The real question is what would you do in Dispose.
At best the only thing you could theoretically do is abort any pending web requests. However, that is probably better left to the app developer to call the right Cancel method – since Load/Submit are all explicit calls, Cancel should be as well.
The existence of IDisposable would be confusing as well – when is it required to be called, and when not, given the lack of concrete scenarios.
Hence no IDisposable on DomainContext.