Triggering Exitcodes in Extensions

Topics: Archive - General, Archive - Toolkit Extensions
Feb 25, 2015 at 9:04 PM
Now that Exitcodes have been standardized (60000+ for TK and 70000+ for Extensions )
What is the best way to trigger them?

In AppDeployToolkitMain.ps1 you guys (The Devs) consistently use:
[int32]$global:executeProcessAsUserExitCode = 60003
Exit
In my Extensions I currently use:
$exitcode = 70008
Exit $exitcode
Should I be using [int32]$global:executeProcessAsUserExitCode instead?
Coordinator
Mar 2, 2015 at 8:47 PM
The correct usage would be Exit-Script $exitCode
Mar 3, 2015 at 2:46 AM
In your latest script there are still Exit <code> instead of exit-script. May be you should get a look.
Do you have a table to define each code?

Thanks,
Coordinator
Mar 3, 2015 at 9:21 PM
Yes we don't call Exit-Script in all scenarios, for example where the toolkit is running asynchronously. Are there any particular issues or instances you are concerned with?
Mar 4, 2015 at 1:48 AM
No, I just would like to know the significance of all exit code as I would like including it in my documentation.