Ah, makes sense. Disappointing, but makes sense.
Thanks.
Search found 4 matches
- Fri Aug 04, 2017 1:26 pm
- Forum: PowerShell Studio
- Topic: PrimalSense Not AutoCompleting Parameters
- Replies: 4
- Views: 1932
- Fri Aug 04, 2017 12:36 pm
- Forum: PowerShell Studio
- Topic: PrimalSense Not AutoCompleting Parameters
- Replies: 4
- Views: 1932
Re: PrimalSense Not AutoCompleting Parameters
Ok, I dug a little further regarding the custom functions. You are correct that it works with custom functions in a .PS1 file, but as soon as the .PS1 file is converted to a module, PowerShell Studio will no longer complete the parameter values while the PowerShell ISE will continue to successfully ...
- Fri Aug 04, 2017 10:04 am
- Forum: PowerShell Studio
- Topic: PrimalSense Not AutoCompleting Parameters
- Replies: 4
- Views: 1932
PrimalSense Not AutoCompleting Parameters
Product, version and build: PowerShell Studio 2017 (5.4.143) 64-bit Operating system: Windows 7 Enterprise Edition (64-bit) or Windows 10 Enterprise Edition (64-bit) The autocomplete feature in the PowerShell Studio script editor does not appear to be working for parameters with ValidateSet validati...
- Fri Aug 04, 2017 9:12 am
- Forum: Wish List and Feature Requests
- Topic: Code Signing Module Script Files Automatically
- Replies: 1
- Views: 4222
Code Signing Module Script Files Automatically
I would like to ask that PowerShell Studio include the feature to automatically update code signing signatures when saving .PSM1 files just as it does with .PS1 files. Our corporate execution policy requires that all PowerShell code be signed in order to execute so editing .PSM1 files is a pain in t...