This relative path is not really useful, I think it should return the full path, otherwise it will be hard for people to load a package and consume it in their automation scripts.
In this example, I used and LLM to create a script to load a fragment and use the MS Intune generator tool to build a package, for demo purposes. The script was generated ok but the the suggested solution to get the source file path was not working because the return path concatenated with the source folder generated an inexistent path, you can see the buggy code at line 49 in the build-intunewin.ps1 script from the share:
Z:\caphyon-users\bogdan\PacKit\PacKit PS Module - demo
Copy the entire folder to test the scripts. Make sure you have the module installed first, the scripts will not install it for you.
This relative path is not really useful, I think it should return the full path, otherwise it will be hard for people to load a package and consume it in their automation scripts.
In this example, I used and LLM to create a script to load a fragment and use the MS Intune generator tool to build a package, for demo purposes. The script was generated ok but the the suggested solution to get the source file path was not working because the return path concatenated with the source folder generated an inexistent path, you can see the buggy code at line 49 in the build-intunewin.ps1 script from the share:
Copy the entire folder to test the scripts. Make sure you have the module installed first, the scripts will not install it for you.