SAPIEN Technologies

I am sure you realized that the files don't actually exist in the folders indicated. The executable resulting from packaging is not created in the same folder as your original script. So you have to copy/move any auxiliary files relative to where the executable is. https://www.sapien.com/blog/2009/0...

You will have to be more specific. External scripts means dot sourced scripts. Modules cannot be resolved and packaged, that would defeat the purpose of a module. Not sure what you mean by it cannot 'see' them. Generally, it is best to provide the code you use to access something and the resulting e...

Please post the code you use to retrieve the stored credentials and indicate where exactly in the form based code you do that.

Advanced Installer has a good number of places where you can specify an executable to do, well, something. 2022-05-12_23-52-55.png The options are usually very specific, as in this example that makes it clear it relates to a 'console application'. Advanced Installer also has a very comprehensive hel...

Do you have the .NET 6 Desktop runtime installed?

These two modules seems to load and add to the cache just fine here, so there must be something else at play.
I attached the files, so you can just copy them in and use the cache editor to activate them.
Your own module you can upload here: https://www.sapien.com/support/upload
I'll have a look

You should not need to run elevated.
The logs would be created here: C:\Users\<User>\AppData\Roaming\SAPIEN\CachedData 2.1\Local Machine
Sorry I did not mention that. Can you check on those please?

As you can see, the module is included in the cached information. 2022-05-09_22-33-50.png The two files (CacheProxyV5.dll and ModuleImporterV5.dll) in the zip go here: C:\Program Files\SAPIEN Technologies, Inc\PowerShell Studio 2022\CacheBuilder64 Please make certain that you make a copy of the orig...

I will upload some updated components for testing shortly. If you are up for some testing. I have been debugging this for a while now, and it seems the following happens: Some modules (without outside reason) load fine but do not report exported cmdlets etc at all on first load. The cachebuilder sav...

Just to keep you in the loop. It appears the az.sql module cannot be loaded correctly when one or more other az.* modules have already been loaded.
We are working on a remedy, please stand by.