Include Module Version in published Module directory structure

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
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.
This topic is 5 years and 8 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
tektim
Posts: 2
Last visit: Sun May 31, 2020 11:20 pm

Include Module Version in published Module directory structure

Post by tektim »

I am a Powershell scripter, have dabbled in a bit of module creation using native PS commands and only recently discovered the Powershell studio Module project & wizards. I have built a simple module containing a couple of functions and built it with the wizard.
I would like to
a) Customise the variables in the generated module manifest file and
b) Version the modules so that when deployed with the "build module" button they are deployed with $ModuleVersion in the target directory structure, i.e. \ModuleName\$ModuleVersion\<ModuleFiles>.

Is this possible with the current product?

Thanks

Product, version and build: PowerShell Studio 2018 v5.5.152
32 or 64 bit version of product: 64 bit
Operating system: Windows 7
32 or 64 bit OS: 64-bit
Powershell version: 5.1.14409.1012
User avatar
tektim
Posts: 2
Last visit: Sun May 31, 2020 11:20 pm

Re: Include Module Version in published Module directory structure

Post by tektim »

Realised I can modify the manifest generated in the Module Project so that's a) sorted. :D
Just need to know if I can customise the Module Build/Deployment process for b).

Thanks
tektim wrote: Sun Jul 01, 2018 6:27 am I am a Powershell scripter, have dabbled in a bit of module creation using native PS commands and only recently discovered the Powershell studio Module project & wizards. I have built a simple module containing a couple of functions and built it with the wizard.
I would like to
a) Customise the variables in the generated module manifest file and
b) Version the modules so that when deployed with the "build module" button they are deployed with $ModuleVersion in the target directory structure, i.e. \ModuleName\$ModuleVersion\<ModuleFiles>.

Is this possible with the current product?

Thanks

Product, version and build: PowerShell Studio 2018 v5.5.152
32 or 64 bit version of product: 64 bit
Operating system: Windows 7
32 or 64 bit OS: 64-bit
Powershell version: 5.1.14409.1012
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: Include Module Version in published Module directory structure

Post by davidc »

The application purposefully doesn't deploy to a version folder because of compatibility issues with older versions of PowerShell.
You could potentially use the Deploy feature to copy the necessary files, but we don't have a preset variable for the module version.

If you would like to see a specific feature implemented. I recommend submitting a request here:

https://www.sapien.com/requests
David
SAPIEN Technologies, Inc.
This topic is 5 years and 8 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.