dispose

问题 I've been familiarizing myself with some of the things (that are planned to be) added in C# 8 & .NET Core 3.0, and am unsure on the correct way to implement IAsyncDisposable (at time of writing, this link has literally no guidance). In particular, it is unclear to me what to do in the case when an instance isn't explicitly disposed - that is, it isn't wrapped in an async using(...) and .DisposeAsync() isn't explicitly called. My first thought was to do that same thing I'd do when implementing

问题 I am writing an ASP.NET Web API. As part of this, I have a class that I found out, during testing, needs to implement IDisposable to ensure managed resources are freed. So, I implemented IDisposable in my class, and put the code necessary to free the resources in the Dispose() method. There are many places in my code (hundreds) where I instantiate this object, and in the same line call a method on the new instance. I only need the instance to call the single method. Here's an example: //

问题 I am writing an ASP.NET Web API. As part of this, I have a class that I found out, during testing, needs to implement IDisposable to ensure managed resources are freed. So, I implemented IDisposable in my class, and put the code necessary to free the resources in the Dispose() method. There are many places in my code (hundreds) where I instantiate this object, and in the same line call a method on the new instance. I only need the instance to call the single method. Here's an example: //

问题 I use NetworkStream with sockets in an SslStream socket server as follows: stream = new NetworkStream(socket, true); sslStream = new SslStream(stream, false); My question is, if when I call sslStream.Dispose() , will the SslStream dispose/close its inner stream and its socket too? Or do I need to explicitly close all three resources with sslStream.Close() , stream.Close() and socket.Close() ? 回答1: If possible, you should use C#'s using construct to dispose the stream 'automatically' after use

问题 I use NetworkStream with sockets in an SslStream socket server as follows: stream = new NetworkStream(socket, true); sslStream = new SslStream(stream, false); My question is, if when I call sslStream.Dispose() , will the SslStream dispose/close its inner stream and its socket too? Or do I need to explicitly close all three resources with sslStream.Close() , stream.Close() and socket.Close() ? 回答1: If possible, you should use C#'s using construct to dispose the stream 'automatically' after use

问题 I use NetworkStream with sockets in an SslStream socket server as follows: stream = new NetworkStream(socket, true); sslStream = new SslStream(stream, false); My question is, if when I call sslStream.Dispose() , will the SslStream dispose/close its inner stream and its socket too? Or do I need to explicitly close all three resources with sslStream.Close() , stream.Close() and socket.Close() ? 回答1: If possible, you should use C#'s using construct to dispose the stream 'automatically' after use

问题 In my program it opens a window if an action is happened. After I have filled out information in this window, and entered a button, the window dispose(). The window is picked up in a program outside my main program, but when I close this window, my main program stops. How can I prevent this from happening? Thanks for your help! 回答1: You can set the defalaultCloseOperation property of the second frame to DO_NOTHING_ON_CLOSE or DISPOSE_ON_CLOSE Don't even use two frames. Use a modal JDialog

问题 I am trying to dispose of my DbContext in my GenericRep from my Generic Service. My generic repo is implementing the pattern described here: https://docs.microsoft.com/en-us/aspnet/mvc/overview/older-versions/getting-started-with-ef-5-using-mvc-4/implementing-the-repository-and-unit-of-work-patterns-in-an-asp-net-mvc-application I have set up the first part in my repo: public class GenericRepository<T> : IGenericRepository<T>, IDisposable where T: BaseEntity { protected readonly

问题 In my backend service I use unit of work pattern. I was wondering if I'm missing something related to disposing objects. First, this is the code I have so far, which works. The service just calls a request handler: [GlobalExceptionHandlerBehaviour(typeof(GlobalExceptionHandler))] public class CustomerService : ICustomerService { public void AddCustomer(AddCustomerRequest request) { ObjectFactory.GetInstance<AddCustomerRequestHandler>().Execute(request); } } The request handler looks like:

问题 In my backend service I use unit of work pattern. I was wondering if I'm missing something related to disposing objects. First, this is the code I have so far, which works. The service just calls a request handler: [GlobalExceptionHandlerBehaviour(typeof(GlobalExceptionHandler))] public class CustomerService : ICustomerService { public void AddCustomer(AddCustomerRequest request) { ObjectFactory.GetInstance<AddCustomerRequestHandler>().Execute(request); } } The request handler looks like: