# Powershell v3 & v2 Compatibilty

**URL:** <https://forums.powershell.org/t/powershell-v3-v2-compatibilty/2718>\
**Category:** PowerShell Help\
**Created:** [June 18, 2014, 12:35am UTC](https://forums.powershell.org/t/powershell-v3-v2-compatibilty/2718 "2014-06-18T00:35:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![powershell-user](https://avatars.discourse-cdn.com/v4/letter/p/cab0a1/32.png) [@powershell-user](https://forums.powershell.org/u/powershell-user)\
**Post date:** [June 18, 2014, 12:35am UTC](https://forums.powershell.org/t/powershell-v3-v2-compatibilty/2718/1 "2014-06-18T00:35:57Z")

</div>

Question -

I am creating scipts in PS version 3 but will be executing them in PS version 2. Is this a problem? Will the scripts fail to execute?

I am in a QA environment. The current server configuration cannot be altered, that means that I can’t get v3 installed along with the necessary modules needed, so I have to create the scripts outside the QA environment and test them as best as I can.

---

<div class="post-metadata">

**Author:** ![richard-siddaway](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@richard-siddaway](https://forums.powershell.org/u/richard-siddaway)\
**Post date:** [June 18, 2014, 12:39am UTC](https://forums.powershell.org/t/powershell-v3-v2-compatibilty/2718/2 "2014-06-18T00:39:40Z")

</div>

Possibly.

If you just use the cmdlets and features that are available in v2 you’ll be OK but if you use any v3 features e.g. the CIM cmdlets you script will fail.

Check the release notes for v3 to see what was introduced and what you need to avoid

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\
**Post date:** [June 18, 2014, 12:49am UTC](https://forums.powershell.org/t/powershell-v3-v2-compatibilty/2718/3 "2014-06-18T00:49:45Z")

</div>

You can start a PowerShell 2.0 session on your development machine by running PowerShell.exe -Version 2.0 . I test scripts this way whenever I’m targeting PowerShell 2.0; no matter how careful I think I’ve been, I always manage to have a couple of 2.0-specific errors that sneak through and need to be fixed before release.

---

<div class="post-metadata">

**Author:** ![nobody](https://avatars.discourse-cdn.com/v4/letter/n/94ad74/32.png) [@nobody](https://forums.powershell.org/u/nobody)\
**Post date:** [June 18, 2014, 3:11am UTC](https://forums.powershell.org/t/powershell-v3-v2-compatibilty/2718/4 "2014-06-18T03:11:10Z")

</div>

Very cool. Is it possible to run Version 2.0 ISE?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\
**Post date:** [June 18, 2014, 3:19am UTC](https://forums.powershell.org/t/powershell-v3-v2-compatibilty/2718/5 "2014-06-18T03:19:36Z")

</div>

Not that I know of, though I never really tried very hard to do that. I hated the v2.0 ISE 🙂

---

<div class="post-metadata">

**Author:** ![dotnVo](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@dotnVo](https://forums.powershell.org/u/dotnVo)\
**Post date:** [May 16, 2024, 8:47pm UTC](https://forums.powershell.org/t/powershell-v3-v2-compatibilty/2718/6 "2024-05-16T20:47:55Z")

</div>

Closed on May 16, 2024, 8:47pm UTC


