DWrite: IDWriteFactory release on library unload

[lb90]

Most users manage the lifetime of IDWriteFactory using a COM smart pointer with static (or thread) storage duration. There are no issues at all when developing an application. However in DLL projects the object's destructor runs from a DllMain notification handler (_DllMainCRTStartup), thus under the loader lock. I wanted to ask if that's a supported scenario for DirectWrite.

For example, IDXGIFactory cannot be created and/or destroyed from DllMain: https://learn.microsoft.com/en-us/windows/win32/direct3ddxgi/d3d10-graphics-programming-guide-dxgi#dxgi-responses-from-dllmain.

Thanks,
Luca

[DarranRowe]

DWriteCreateFactory is in dwrite.dll. If you link against dwrite.lib then dwrite.dll will be loaded as a dependency of the DLL. The various objects that DWrite use all appear to be implemented in dwrite.dll, so just linking against dwrite.lib should be enough to deal with all issues.