Howard Kapustein
Howard Kapustein
@malxau > I don't see a way to pass command line arguments to the installer in winget, but this is important to get a silent install It's supported. For instance...
Is -ff needed? Footprint files are unique filenames; you can't put a 'content' file in an MSIX named `appxmanifest.xml` or `signature.p7x`. Filenames are unique so -f appxmanifest.xml would work equally...
Please change the 'bug' label to 'Feature'. Sorry about that.
Please change the 'bug' label to 'Feature'. Sorry about that.
>What's the recommended approach to load the dlls to which path is defined in environment variable "path"? To not rely on the PATH environment variable. That's a rather fragile way...
By "it" are you asking how to build *WinAppSDK*?
Does this happen when you install WinAppSDK runtime 1.1.4 as the 1st/only WinAppSDK packages on the machine? When 1.1.3 is installed and you update to 1.1.4? There's an odd ACL...
> * v1.1.3: ` BUILTIN\Users:(I)(RX)` > * v1.1.4: ` BUILTIN\Users:(R)` That is extremely interesting. Do you know the repro to produce this? Would this be in the above 13 steps...
> ## 1.1.3 > ... > 3. Check ACLs (`icacls "...x86..."`), see ` BUILTIN\Users:(I)(RX)` x86 but the 1.1.4 ICACLs is for x64. Wrong path? (but same result?)
>only has one 'Users' entry, not 4 And notice the last 2 Users have Conditional ACEs(?) for Microsoft.WindowsAppRuntime and ***YourPhone***? YourPhone is a packaged app using WinAppSDK but I wouldn't...