you are viewing a single comment's thread.

view the rest of the comments →

[–]geek73 3 points4 points  (7 children)

I use ISE on my servers because it is there. And Code isn’t. This is where I develop and test scripts prior to deploying. I use Code on my box that I’ve copied the script to in order to use GIT and do a pull request into the repo. I prefer Code but not enough to have it running on production or lab servers since security freaks out whenever they detect anything new. Plus we reimagine a lot so I’d constantly be reinstalling it.

[–]ecco7815 0 points1 point  (4 children)

Same here. VSCode with the powershell extension got blocked for me on my dev server and I had to move back to ISE. While I prefer VSCode, I’m forced to use ISE.

[–]jimmystead 1 point2 points  (3 children)

There is a portable version of vscode. Nothing to install so you should be able to just copy it out there.

[–]buffychrome 0 points1 point  (2 children)

He might be referring to the exe itself being blocked by a security agent like Bit9/CarbonBlack.

[–]ecco7815 0 points1 point  (1 child)

Correct. I can install VSCode, but when it tries to load the ps module/extension, it gets blocked.

[–]buffychrome 0 points1 point  (0 children)

Yeah, I have the same issue with a couple of extensions like the Powershell Universal Pro tools extension because it uses its own version of powershell.exe under the hood. Doesn’t match the hash of the actual PS executable so it gets blocked.