I've been using Powershell Studio 2014 for a bit ...
First of all: Thanks! Generally working well and the new features are in most cases great. Most cases.
So here's the list of things I'd love to have, that I think might be within reach of reasonable development effort:
Script Formatter
Really a "WoW!" feature. Never was steal... *cough* borrowing other people's script simpler (Yes, I do keep the credits note, not to worry). The thing is, however: Would you mind including Comments for functions in it?
- Remove trailing spaces/tabs in comment lines
- Take care of proper indentation.
- Notify of invalid Comment entry points (like ".PAREMETER" instead of ".PARAMETER"). Those cause the comments to be invisible when calling the help cmdlet on the commented function.
Prefered Comment Location
For both the function builder (great feature, I like it a lot) and - if I get it - Script formatter I'd like to have the option to place the comment inside the function, instead of above it.
So, not ...
PowerShell Code
Double-click the code block to select all.<# .... #> function Test-Function { param(... but rather ...
PowerShell Code
Double-click the code block to select all.function Test-Function { <# .... #> param(On that note, while I'm at it: Thanks for implementing the option to select whether the opened curved braces are to be placed at the end of a line or at the beginning of the next. I remember asking for it some time back and I've been told it's nice to express gratitude when other people fulfill your whishes
Running Scripts
I would like to have the option back, to run a single file within a project, instead of having to either run the entire project or copying the page to an individual script.
I have to do that frequently, so it'd be a big time-saver for me.
Function Validator
One nice feature I'd kind of like, and which might be within reach, given your Script formatter: An option to validate a function.
- Are all comments set?
- Have the Parameter Object types declared?
- Probable conflicts when using multiple validations on a single parameter?
- Is the Begin, Process, End Block there and well-designed?
I think it might be a good idea to implement that as a separat menu, where the individual checks can be toggled/untoggled and the functions to be validated can be chosen...
Enhanced MSI Packager
I like the new MSI Packager, but I can't use it. Not because it doesn't work, but because the result can't be made compliant to company policies. What I'd like to have ...
... the choice for the install-path. (Like $env:ProgramFiles\[CompanyName]\[Category]\[SubCategory]\[Name])
... the ability to install x64 packages into the x64 ProgramFiles folder on x64 Systems.
Script Packager
The script packager updates are great. Except for that minor thing, that it's more cumbersome to package a project for multiple architectures. I need to assemble most of my products for both 32-Bit and 64-Bit environments, as well as for Windows 6.1 and 6.3 operating. This means I need to build 4 packages for each Project / File. Version 2 x86, Version 2 x64, Version 3 x86 and Version 3 x86.
This is due to the inability to rely on which version of .NET is available, what kind of APIs it has to interact with, etc.
Oh, and each needs to have a different, specific name, of course.
Sooo ... could I get the option to register multiple packages? So that when I build a package, it builds all four packages for the simple effort of one klick?
And that's all of my new requests ... for now
Cheers,
Bosparan