![]() ![]() ISE has no conditional break points, no function break points and no ability to connect to an existing PowerShell process and debug it. ![]() When things are really in the ditch, there is no comparing the debugging capabilities between PowerShell ISE and VS Code.Some folks will insist on using only the Git command line tools, but if you are trying to grow skills of a team, it's a lot easier to see changes and do things like "CTRL-ENTER" to quickly perform commits. There is no built-in integration with other stuff like Git, InvokeBuild, Pester, PSScriptAnalyzer, Markdown, JSON, XML, etc. As one moves from "Tool User" to "Tool Maker" it gets pretty easy to outgrow the ISE. ![]() One can't use PowerShell 7.x with the ISE, and if you resist using PowerShell versions past Windows PowerShell 5.1 you are missing out on any improvements in PowerShell made in the last SIX (6) years. VS Code one must admit to still using Windows PowerShell 5.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |