PowerShell Studio Feature Requests
Feature requests, product enhancement ideas, and other product-specific suggestions.Additional functionality for the...
Automatically remove trailing whitespace
Restrictions Options
Better text manipulation
Wrap selected text with quotes or brackets
Duplicate Current Selected File
Multiple File Browser windows/tabs Or a...
Allow a configurable Module Folder for module...
Open Folder also in Project Panels
Faster Code Checking
default icon
Multiple line Debuger Console and Wordwarp...
Build order for Project
Build order for Project
Add GitHub Copilot integration
Add Comment/Block Comment/Uncomment to...
Import Existing Forms
Bracket Pair Colorization
Sort Selected Data/Code
Console Colors: please expand to 24-bit
Collapse Class
Automatically complete list Accurate matching
Change PowerShell 7 Warning to Once a Day or...
Expanding Snippet Variable Names...
SSH Remote connections
Add PrimalSense support for $PsSenderInfo...
Add "Do not execute unless PowerShell...
Bracket pair colorization
Add the ability to add custom file extensions...
Fix TreeView control double click
Create SAPIENHost object for Service host
Collapse All
Add buttons to save /restore Console setting.
Add ability to customize layout settings for...
Ability to select subfolder in Windows start...
Add Git Context menu in editor Script pane
Git Context menu in File Browser pane.
Basic YAML Syntax Highlight
Collapse Entire Function
Add Spellcheck
High-contrast theme request
Selected PowerShell version for launching...
Environmental Controls for the UI
"Compact" PowerShell 7 Option
SAPIENT PowerSHell 7.x Host (Silent)
Integrate WebView2
Editable Console during GUI / script run
Collapsible sig block
Add support for Pester in Regions
Listview default view should be 'Details' not...
Git Source Control - Coloring Files in File...
Provide the option to "automatically check...
JobTracker Suggestion
Current Line Highlighted during Debuging
Add output folder browser to package output...
PowerShell Studio training
Search for Pester test files in subdirectories
Show the hierarchy of GUI elements and make...
Multi Languge GUI development
Manage Recents Window
Expose Icon for Windows Tray App
Dark Theme strips
Building a working package using PSBuild.exe...
Sync Profile Settings
Code folding for Pester blocks
Support for EditorConfig
Disable Script Block logging while running -...
Format C++ Script
Provide for dot source module structure
Show white spaces - Option to hide newline...
Implement Tab Order Menu to set Tab Index
Variable declaration formatting
Primalsense missing loop keywords break,...
Customizable Keyboard Shortcuts for...
Shortcut to duplicate a line CTRL+D
Search in the new Recents Lists
Allign value variable
Select highlighted Intellisense drop down...
Add a Way to Disable Font Resizing in the...
ALT+ arrow up & ALT + Arrow Down
OSX/Linux Version(s) of PowerShell Studio
Find & Replace Enhancement
File Browser Panel
Auto fill end condition commentary
Have snippet manager follow PSS Studio theme
More Robust GitHub Integration
GitHub token support for SAML-enabled orgs
Utilize Chocolatey for a quick download of...
Adding Web Support
Automatically add new functions to module...
Prevent "Edit Function" function from making...
Implement Windows Community Toolkit
Add more recently opened files to the start...
PrimalSense for dot sourced script variables
Simpler way to validate ps1 certificate /...
Password input field when signing code with...
Auto-Add New Forms to project
Make diff's of .psf files useful
AutoComplete with parenthesize
Make diff's of .psf files useful
ALIENQuake, Jun. 29, 2019Denied:
There are no plans to change psf file format.
Every time when I modify a form, there is a huge change of 'xml data' part inside file. Same thing when I replace resource image with another.
The diff's are huge and it's very uncomfortable to see actual code changes. I'm aware that this is because of psf merge some code + data.
Spliting psf files into two:
- one with actual code
- one with xml data
would be easiest solution.
Comment by brittneyr, Sep. 19, 2019
Psf files are form projects and contain all the information for the designer. Have you tried exporting the forms to ps1 script files before comparing?
Comment by ALIENQuake, Oct. 2, 2019
@brittneyr
The "psf" files also contains my custom code for the application. If the custom code (and only code) associated with form would endup inside separate file, it wont be a problem. Spliting psf file into two shouldn't be a problem, espacially when you consider 'exe' distribution.
Are you suggesting that I should export all "psf" files as ps1, commit those extra ps1 files into git and then, after every single change of "psf" repeat this process so I could look at the differences of exported ps1 files and not actuall "psf" files? I'm sorry but I don't accept you suggestion as valid.
Very important advantage of using source control is to see changes between two commits. The current "psf" design" prevents it. I'm sure that putting all into "psf" files was done for some reasons. But if the outcome prevents seeing changes between two commits, it's very big drawback. It prevents code cooperation and rewiews. Just image how "psf" diffs would look inside email messages.
Please rethink the current "psf" design.
