To help you better we need some information from you.
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product, version and build: PowerShell Studio 2018, 5.5.149
32 or 64 bit version of product: 64
Operating system: Windows 10
32 or 64 bit OS: 64
*** Please add details and screenshots as needed below. ***
I have recently noticed that when Deploying a module, PowerShell Studio is stripping out the #Requires directives. When did this start happening, and can that be turned off?
DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
Module Deployment Process
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
Re: Module Deployment Process
Thank you for reporting this we are taking a look into this and will report back when we know more.
Re: Module Deployment Process
This issue will be resolved in the next service release.
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Module Deployment Process
We released a new service build (v5.5.150). Please let us know if the issue persists.
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.