Additional hint for the summary of IPortableDeviceContent::CreateObjectWithPropertiesAndData

[NilsHoyer]

In your description of IPortableDeviceContent::CreateObjectWithPropertiesAndData I would like to have a hint, that the stream must be released and how I should do that.

https://learn.microsoft.com/en-us/windows/win32/api/portabledeviceapi/nf-portabledeviceapi-iportabledevicecontent-createobjectwithpropertiesanddata

Same for IPortableDeviceResources::GetStream:
https://learn.microsoft.com/en-us/windows/win32/api/portabledeviceapi/nf-portabledeviceapi-iportabledeviceresources-getstream

PS I use a Marshal method for releasing and that works fine for me. But I mention this after I spend 30 to find this out (call me "stupid" if you want 🤫).

[dahall]

For both methods, the XML comments exactly match those in the links you provided. Was there more you think is needed?

[NilsHoyer]

I didn't find this text in VS 2022:

The SDK allocates this memory, and the caller must release it using CoTaskMemFree.

[dahall]

Right. The .NET framework, when marshaling strings, will internally call CoTaskMemFree on them before returning the string.

The IStream parameter does have the correct text for what needs to be done.

The caller must release this interface when it is done with it.

[NilsHoyer]

I'm using Marshal.ReleaseComObject(stream):
https://learn.microsoft.com/de-de/dotnet/api/system.runtime.interopservices.marshal.releasecomobject?view=net-8.0

If I don't call it, I can't use both mentioned methods again. While trying it, I get a message, that a resource is busy. (Sorry, at this moment I can't provide the correct error code or message.)

[dahall]

Good. You're doing exactly what the documentation requires, but in .NET fashion.

[NilsHoyer]

... and I believe, this hint inside your description would be helpful for other people. Because of this, I opened this issue.

[dahall]

Added that note to those methods.

[NilsHoyer]

Your changes are exactly, what I hope other developer helps. Thank you!