✨ handling PSADT deploy-application.exe

I've added feature that allows to test your PSADT based apps in Sandbox.
What is PSADT? Check here - https://psappdeploytoolkit.com/

What are requirements to use this feature?
Add "PSADT" suffix to a folder which contains your app and all PSADT items.
Like:

Insides:

Changes in Invoke-IntunewinUtil.ps1:

if ($Folder.FullName -like '*PSADT'){
    $ArgumentList = "-c `"$($Folder.FullName)`" -s `"$($Folder.FullName)\Deploy-Application.exe`" -o `"$($Folder.FullName)`" -a `"$($Folder.FullName)`" -q"
} else{
    $ArgumentList = "-c `"$($Folder.FullName)`" -s `"$($Folder.FullName)\$($Folder.Name).ps1`" -o `"$($Folder.FullName)`" -a `"$($Folder.FullName)`" -q"
}

v.1.3.1 - New feature! Run test with detection script

Changelog

1.3.1

As an Intune advanced users we all need to use custom detection script from time to time.
Now you can also incorporate your detection script into testing flow in Sandbox!!

New context menu has been added for that! ✨
Run test in Sandbox with Detection

Detection is ran before installation and if it failed to detect ( exit code 1 ) installation is started.
After installation is finished detection is ran again.

To use new feature, update module from PSGallery and then run Update-Sandboxshell from module 😁

v1.2.0 - Rebuild project to PSModule

Changelog

1.2.0

The idea behind creating PSModule from project is to ease installation and update process.
Additionally to that I've created pipeline with Pester tests, PSScript Analyzer and publish to PSGallery 😃

• To install module you will be able to invoke cmdlet Install-Module Intune-App-Sandbox
• To apply project to your workstation run Add-SandboxShell
• To update project firstly run Update-Module Intune-App-Sandbox then Update-SandboxShell

https://www.powershellgallery.com/packages/Intune-App-Sandbox/1.2.0

[New feature] Toast notifications within Sandbox

Changelog

1.1.0

While process overall hasn't changed, I've added feature which uses Windows toast notifications to provide user with information regarding current step in process and final exit code.
What changed:

• Added toast.xml - it contains template configuration for toasts which are displayed.
• Added New-ToastNotification.ps1 - function which invokes toast notification. It takes parameters:
  • XmlPath
  • Title
  • Body
• Modified Invoke-Test.ps1 - now script creates 2 files (_LogonCommand, _PreLogonCommand). _PreLogonCommand prepares environment for use of toast notifications. And then runs _LogonCommand which kickstarts installation process.
• Reduced scheduled task delay from 60 second to 15 second - yeey