PowerShell.MCP v1.2.6 - Enhanced Text File Operations with Automatic Encoding Detection #8
yotsuda
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Enhanced Text File Operations with Automatic Encoding Detection
This release focuses on improving cmdlet naming clarity and automatic encoding detection.
✨ What's New
🔄 Renamed Cmdlets for Better Clarity
Text file cmdlets have been renamed to better reflect their functionality:
Migration Guide:
Update-TextFile→Update-MatchInFileSet-LinesToFile→Update-LinesInFile🔧 Enhancements
🌐 Automatic Encoding Detection
All text file cmdlets now automatically detect and preserve file encoding, ensuring data integrity across different character sets:
Key Benefits:
🐛 Bug Fixes
UTF-8 Encoding Preservation
📚 Dependencies
Added Ude.NetStandard (Universal Charset Detector)
Improved Positional Parameters
Update-LinesInFile - LineRange is now positional for cleaner syntax:
Important: When replacing multiple lines, pass an array with matching number of elements:
Backup Feature
All modification cmdlets support the
-Backupparameter:Backup files are named with timestamp suffix, allowing multiple backup versions.
📋 Complete Feature Set
All Text File Cmdlets
🔄 Installation & Upgrade
Update MCP Configuration
(Get-Module PowerShell.MCP).ModuleBase{ "mcpServers": { "PowerShell": { "command": "C:\\Path\\To\\PowerShell.MCP\\1.2.6\\bin\\PowerShell.MCP.Proxy.exe" } } }📖 Full Guide: https://github.com/yotsuda/PowerShell.MCP#quick-start
💡 Usage Examples
Full Documentation: https://github.com/yotsuda/PowerShell.MCP
Questions? GitHub Discussions
⚠ Security Notice: Provides complete PowerShell access. Use in trusted environments only.
This discussion was created from the release PowerShell v1.2.6 - Enhanced Text File Operations with Automatic Encoding Detection.
Beta Was this translation helpful? Give feedback.
All reactions