Product: PowerShell Universal
Version: 4.3.4
Hi All,
So we seem to have an issue where our custom modules aren’t updating and we can replicate this on our dev server as well as prod server.
I reproduced this by creating a test app with a button to sync a dynamic region which runs a newly added function in the module file. The result was an error that says “The term ‘New-RNG’ is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.”
Context:
- Our instances sync with Azure devops and we create the modules using VS code
- After the sync I can see that the folder structure has been created on the server where the modules are kept “ModuleDir > Example Module > v1.0.0 > module files”
- When looking in our admin console the module explorer doesn’t display the module and if I try to create a module with the same name and version number within the admin console there are no errors and it still does not display within the console
- To get the custom module to work I have to delete the module folder on the server, recreate it in the admin console and then copy and paste the code we have from VS code
- If we make a change or add a function to the module file (directly from the admin console or from VS code and syncing) its like PSU doesn’t recognise or apply the change. Module discovery or restarting the PSU server doesn’t fix the issue.
- The only way to get it working is to delete the module from PSU, recreate it in the admin console and copy/paste the code in and submit it
Has anyone else had this issue or know a fix?