idisposable

I am just learning the Entity Framework and have made some good progress on incorporating it with my layered code structure. I have 2 visual layers, a business layer and a data access layer. My problem is in passing entity object between layers. This code sample does not work: // BLL public static void Test1() { List<User> users = (from u in GetActiveUsers() where u.ID == 1 select u).ToList<User>(); // Do something with users } // DAL public static IQueryable<User> GetActiveUsers() { using (var context = new CSEntities()) { return from u in context.Users where u.Employee.FirstName == "Tom"

I am trying to develop a library using dependency injection approach (with Ninject) and I am having some kind of confusion likely because of my incorrect design. In summary, my design approach is A parent object has a common object. A parent object uses some variable number of child objects. All child objects should use the very same common object instance with their parent object Here is a simple model of my problem domain. interface IParent : IDisposable { void Operation(); } interface ICommon : IDisposable { void DoCommonThing(); } interface IChild1 { void DoSomething(); } interface IChild2

My question is why do I need IDisposable? I have a class that consumes some resources that need to be freed. I have two options Without IDisposable class SomeUtilityClass { public Stop() { // free resources } } With IDisposable class SomeUtilityClass, IDisposable { public void Dispose() { // free resources } } So why do I need IDisposable here? It does not matther how to name the function. class Program { public Main(..) { SomeUtilityClass _class = new SomeUtilityClass(); // clean up when we've done _class.Stop(); // OR _class.Dispose(); } } Because IDisposable is supported by C# and you can

If I have code with nested objects like this do I need to use the nested using statements to make sure that both the SQLCommand and the SQLConnection objects are disposed of properly like shown below or am I ok if the code that instantiates the SQLCommand is within the outer using statement. using (var conn = new SqlConnection(sqlConnString)) { using (var cmd = new SqlCommand()) { cmd.CommandType = CommandType.Text; cmd.CommandText = cmdTextHere; conn.Open(); cmd.Connection = conn; rowsAffected = cmd.ExecuteNonQuery(); } } Yes. You could clean it up a little like this using (SqlConnection conn

I've got a form that creates a couple of disposable resources in its constructor that I need to dispose of. However, the C# form designer already produces a Dispose() method in the Designer.cs file that doesn't appear to have any type of user hook in it. So I'm at a loss as to how I'm supposed to implement the typical IDisposable pattern. This form is occasionally created but never shown, so using the Close event won't help. The objects in question are not IComponents , so I can't just add them to this.components . Where can I put this clean-up code and be sure it will run when the form is

I use StreamResourceInfo.Stream to get BitmapImage s from resources. Is it correct to Close and Dispose the stream after using it? I ask because in memory profiler, I get an error if I do so. Memory profiler says that a disposed instance has not been GCed. If I look on the web, I only can find this post to this topic. In this post, the responding person says, that it is meaninfull to dispose. However if I look at the circumstances and on the effect, I don't think that this is right. Does someone know what is the right action? Additional information: In the msdn examples I have seen, they don't