Ayende @ Rahienhttp://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Mladen commented on Entity Framework: If you pass a connection to the context, you are responsible for disposing itahhhhhh.... now i got it. If you pass any connection into it! DOH! http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment5http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment5Sun, 26 Sep 2010 14:13:58 GMTAyende Rahien commented on Entity Framework: If you pass a connection to the context, you are responsible for disposing itMladen, How is EF to know that you didn't pass it from someplace totally different? http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment4http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment4Sun, 26 Sep 2010 13:57:30 GMTMladen commented on Entity Framework: If you pass a connection to the context, you are responsible for disposing itMaybe i'm misunderstanding something here but how is new-ing an EntityConnection using an existing connection? if you do: new MyContext(new EntityConnection("name=MyConStr")) shouldn't that create a new connection in that context? maybe EF does this differently but i haven't worked with EF yet, so maybe i'm missing something here. http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment3http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment3Sun, 26 Sep 2010 13:54:31 GMTconfigurator commented on Entity Framework: If you pass a connection to the context, you are responsible for disposing itIndeed, classes that accept parameters should not dispose of their parameters; whoever opened the connection should be responsible for closing it. StreamReader and StreamWriter fail miserably there. Try using (MemoryStream s = new MemoryStream) { using (StreamWriter writer = new StreamWriter(s)) writer.write(something); s.Seek(0); using (StreamReader reader = new StreamReader(s)) reader.ReadToEnd(); } http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment2http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment2Sat, 25 Sep 2010 21:15:04 GMTDamien Guard commented on Entity Framework: If you pass a connection to the context, you are responsible for disposing itThis applies to LINQ to SQL too - if the connection is a string it will open and close, if it is an existing connection it will not. [)amien http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment1http://ayende.com/4640/entity-framework-if-you-pass-a-connection-to-the-context-you-are-responsible-for-disposing-it#comment1Sat, 25 Sep 2010 17:22:24 GMT