The focus in these steps will be specific to using PowerShell with SQL Server, but I have to cover some of the basic things. Yet, again, only you can make that decision, based on what you are doing, where you feel comfortable, and what you like / prefer.This article is the first step among many that I hope will help give you a foundation of knowledge to get started utilizing PowerShell. My Rule of thumb: Use the right tool for the job. VS - N-Tier, WPF, DLL, web and mobile dev VSCode - with several extensions and customized to get as close to the ISE as possible ISE - with several add-ons (Module Browser, Project Explorer, Script Browser, Script Analyzer, Variable Explorer, Function Explorer, WMI tools, a bunch of customer add-on code ) There will always those who prefer one over the other. Yet, as I said I have an use PSS for major projects (WinForm GUI, EXE, etc.) and VSCode (Win, OSX and Linux) for other stuff, but I also use Visual Studio for other development needs that often includes PoSH code as part of a target project. You know the ISE, and like you, I've lived in it since it was first introduced. Regardless of what other may infer or try to convince you of.
Only you can decide what is best for you. ISE has a lot of features that is not in the VSCode, and VSCode has a lot of features, that are not in the ISE. Just know that the ISE is what it is now, and no more work is going into it. Yet, since it has to ben installed everywhere you will use it, then the ISE is the choice, since it is built-in. If you need fast, light, cross platform tool, then VSCode is it. If you are not really doing major projects, UI design, etc., then it a really overkill vs what the ISE or Visual Studio Code does. Yet, I've been a developer for years, thus used to heavy tools. However, it is a full blown development suite much like Visual Studio. For major PoSH projects there is no substitute, IMHO.
0 kommentar(er)
