![]() ![]() ![]() I was more referring to stuff that would cause a memory leak or OS instability if you didn't free it up like say COM objects or unmanaged bitmaps, that sort of thing.īut to your original point, my worker thread is specifically a foreground thread because I WANT it to "hang" / keep the process alive until its done. You mean as in and Tasks? Well, personally, I'm conscientious about cleaning up everything I create, but threads and tasks clean themselves up when they exit. Like the type of people who rather then fix memory leaks in applications simply write scripts to reboot the machine daily type of people. Like the type of people who milk a literal 5 minute task for 6 months to a year type of people. I know I'm sounding picky by not wanting to add any additional burden on developers that I don't need to, but you'd have to understand the type of people I work with to understand why. That is *very* rare in my world as 99.99999% of our stuff is strictly managed. Calling Dispose() on the container is only a requirement if the container contains objects with unmanaged resources that need to be freed up. It wouldn't get disposed unless the user manually called Dispose on the container. The API is implemented as a service (in the DI / SL sense of the word service, not as a Windows Service), so the instance of my API ends up being a static singleton instance inside of the DI container. Mind you, I'm not trying to argue with you (just in case you are starting to get annoyed lol). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |