-
-
Notifications
You must be signed in to change notification settings - Fork 807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate PowerShell 2.0 Support #163
Comments
Allow Powershell 2 support deprecation warning to be suppressed by importing the module with a true value as an argument. The ability to pass arguments through Import-Module is pretty limited, accepting only positional arguments, but it still seems a preferable option to environment variables or asking users to modify posh-git directly. Closes dahlbyk#163
Allow Powershell 2 support deprecation warning to be suppressed by importing the module with a true value as an argument. The ability to pass arguments through Import-Module is pretty limited, accepting only positional arguments, but it still seems a preferable option to environment variables or asking users to modify posh-git directly. Closes dahlbyk#163
just getting this warning now. but the link suggested: This download includes Windows PowerShell 3.0, WMI, WinRM, Management OData IIS Extension, and Server Manager CIM Provider Does not donwloading this mean I can't use github for windows, or github anymore ? |
@Neon22 what version of Windows Server are you using? You might try jumping straight to PowerShell 4.0 or PowerShell 5.0? |
oh... completely unaware - good solution - thanks... |
Done: 83caec1 |
Hrm... well, I just now started getting the "get version 3.0" warning yesterday. I'm still using windows 7 and those links to get the newer powershell just take me to an "upgrade to windows 10" link, which I don't really want to do. Any suggestions aside from telling me to upgrade to windows 10? Would it hurt anything to just suppress the warning for now? |
fwiw, I have to dev on an x86 win7 machine for a current client, and was able to successfully upgrade Powershell on that dinosaur :) |
so how do I do that? Links to instructions would be wonderful.... going to google it, but hopefully maybe you'll have some direction for me as well. |
sigh Never mind and thanks for the replies. I just realized the link only has an advert for windows 10... not that I have to install it.... hehe. Sorry all! |
Which OS and architecture (32- or 64-bit) do you have? |
Where is the setting to disable the warning |
$NoVersionWarn, https://github.com/dahlbyk/posh-git/blob/master/posh-git.psm1
|
dahlbyk commented on Jun 10 i have windows 7 ultimate 64-bit |
Vista = Windows6.0 x86 = 32-bit So for Win7 64-bit you want |
ty |
I am on Windows Server 2008 R2. Will probably look for something else then. |
2008 R2 is Windows6.1, so would use Windows6.1-KB2506143-x64.msu |
PowerShell 4.0/ PowerShell 5.0/ PowerShell 3.0 are not fit my PC ,can not updata ,what I can do next |
What OS are you using that you're unable to upgrade to PS 3? I'm not all that interested in trying to preserve compatibility with Vista or XP, but you could certainly maintain a fork that maintains PS 2.0 compatibility and back-ports new features. Or just use an older version of posh-git. |
To lose the above error I d/l'ed and installed Win7AndW2K8R2-KB3134760-x64.msu on my Win7 SP1 system (twice) as instructed then rebooted as it requested, and /still have the error/. The only folder I see under C:\Windows\System32\WindowsPowerShell is v1.0. (Just FYI; I'm giving up on this for now.) |
The folder name |
Good to know, thanks.
|
|
Good call! thanks: |
Dropping support for PowerShell 2.0 means fewer workarounds like #162. Before we do so, it would be good to warn those using 2.0 about the change:
The text was updated successfully, but these errors were encountered: