COM+ keeps file handles locked after work is done
Posted: 2011-05-14T10:05:27-07:00
I'm using the COM+ component in C# as documented in this post http://blog.boundingboxgames.com/2011/0 ... s-xna.html to create temporary files in a game asset pipeline which are read back in after processing.
Unfortunately it appears the COM+ object keeps the file handle open until the COM+ object is finalized. This makes it impossible to use it to repeatedly to generate a temporary file that is read back in by the tool and then deleted.
Ideally the COM+ object would release file handles immediately upon completing work, or if that's not possible for some reason, provide an explicit Dispose interface to allow the caller to trigger the cleanup as needed.
Thanks
Unfortunately it appears the COM+ object keeps the file handle open until the COM+ object is finalized. This makes it impossible to use it to repeatedly to generate a temporary file that is read back in by the tool and then deleted.
Ideally the COM+ object would release file handles immediately upon completing work, or if that's not possible for some reason, provide an explicit Dispose interface to allow the caller to trigger the cleanup as needed.
Thanks