You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So IME has AgentExecutor and you can see the Windows Store calls invoking the WingetCOM server for facilitating those installs.
I have a bunch of cmdlets and stdout checks to interact with the winget source for installs. It works, but it is sort of fragile with how the Program is created.
I can see the https://github.com/microsoft/winget-cli/tree/master/tools/SampleWinGetUWPCaller/AppInstallerCaller example, but yeah was hoping to not have to remember my CPP days. 😅 Hypothetically I could use that as an inspiration to write a helper EXE to run from Intune, but given it seems like AgentExecutor already has the hooks I didn't know if we could call AE in the Program entry so it could do all the WingetCOM stuff auto-magically.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
So IME has AgentExecutor and you can see the Windows Store calls invoking the WingetCOM server for facilitating those installs.
I have a bunch of cmdlets and stdout checks to interact with the winget source for installs. It works, but it is sort of fragile with how the Program is created.
I can see the https://github.com/microsoft/winget-cli/tree/master/tools/SampleWinGetUWPCaller/AppInstallerCaller example, but yeah was hoping to not have to remember my CPP days. 😅 Hypothetically I could use that as an inspiration to write a helper EXE to run from Intune, but given it seems like AgentExecutor already has the hooks I didn't know if we could call AE in the Program entry so it could do all the WingetCOM stuff auto-magically.
Beta Was this translation helpful? Give feedback.
All reactions