Using a LGPL library in a MSIX package

%3CLINGO-SUB%20id%3D%22lingo-sub-1535743%22%20slang%3D%22en-US%22%3EUsing%20a%20LGPL%20library%20in%20a%20MSIX%20package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1535743%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3Ewe%20are%20considering%20to%20use%20a%20library%20under%20the%26nbsp%3BGNU%20Lesser%20General%20Public%20License.%20If%20I%20understood%20the%20license%20correctly%2C%20this%20means%20we%20need%20to%20provide%20the%20user%20with%20the%20option%20of%20replacing%20the%20library%20.dll.%20But%20if%20I%20understand%20it%20correctly%20MSIX%20packages%20don't%20allow%20to%20dynamically%20link%20to%20libraries%20that%20are%20not%20part%20of%20the%20package.%20Is%20this%20the%20case%3F%20Is%20there%20a%20way%20to%20comply%20with%20the%20requirements%20of%20the%20GNU%20LGPL%20in%20a%20MSIX%20packaged%20product%3F%3CBR%20%2F%3EGreetings%2C%3CBR%20%2F%3EDominique%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1539383%22%20slang%3D%22en-US%22%3ERe%3A%20Using%20a%20LGPL%20library%20in%20a%20MSIX%20package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1539383%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F734997%22%20target%3D%22_blank%22%3E%40DominiqueFrost%3C%2FA%3E%26nbsp%3BOne%20could%20make%20an%20argument%20that%20it%20is%20possible%20for%20the%20end-user%20to%20create%20a%20Modification%20Package%20in%20the%20MSIX%20Packaging%20Tool%20that%20has%20the%20replacement%20library.%26nbsp%3B%20The%20key%20would%20be%20that%20your%20placement%20of%20the%20library%20in%20the%20package%20will%20need%20to%20be%20in%20a%20common%20(VFS)%20folder%20location%2C%20and%20you'd%20need%20to%20document%20that%20location.%26nbsp%3B%20So%20placing%20in%20the%20the%20VFS%5CSystemX86%20or%20VFS%5CSystemX64%20folder%20probably%20works.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hello,

we are considering to use a library under the GNU Lesser General Public License. If I understood the license correctly, this means we need to provide the user with the option of replacing the library .dll. But if I understand it correctly MSIX packages don't allow to dynamically link to libraries that are not part of the package. Is this the case? Is there a way to comply with the requirements of the GNU LGPL in a MSIX packaged product?
Greetings,
Dominique

1 Reply

@DominiqueFrost One could make an argument that it is possible for the end-user to create a Modification Package in the MSIX Packaging Tool that has the replacement library.  The key would be that your placement of the library in the package will need to be in a common (VFS) folder location, and you'd need to document that location.  So placing in the the VFS\SystemX86 or VFS\SystemX64 folder probably works.