New
#30
Either
- Windows Powershell
- Windows Powershell (x86)
- Windows Powershell ISE
Should work
However if you are not familiar with Powershell maybe give the tutorial a walk through.
OneGet needs the Windows Management Framework version 5 which is native in Windows 10 and can be downloaded and installed on earlier versions of Windows here: Download Windows Management Framework 5.0 Preview February 2015 from Official Microsoft Download Center.
A quote from the above mentioned site:
However, Garret Sercak (head of OneGet team at Microsoft) has had a habit to publish OneGet experimental builds as the project evolves. You can check @PSOneGet on Twitter for download links for the latest build. I have only tested these experimental builds in Windows 10 but can't see any reasons why they wouldn't run in Windows 7 PowerShell.Supported Operating Systems
- Windows 8.1, Windows Server 2012, Windows Server 2012 R2
- Windows Server 2012 R2
- Windows 8.1 Pro
- Windows 8.1 Enterprise
- Windows Server 2012
Latest experimental build was released only three days ago:
Tweet
— Twitter API (@user) View on Twitter
A good OneGet alternative for Windows 7 is Chocolatey. This tutorial is for Windows 8 but Chocolatey works exatly the same way in Windows 7: Chocolatey - Install Apps from Command Line
Kari
BunnyJ,
I am actually considering sticking with windows 7 and my current dual boot. I am not really sure I like Zdnet reporting of microsoft windows 10 lifecycle policy. It even changes the future if I even buy a computer that has windows as a service. I also thought the current version of the windows 10 had spartan in it, from what I read it doesn't.
I even updated to the 3.0 powershell and even an unofficial script to install one-get beta nothing worked.
However, Choco works though.
I got interested, installed Seven on a vm, now upgrading it's Management Framework to v.3 in order to be able to upgrade PowerShell to v.3, after that the experimental build should run. I'll post the results of this test.
PS C:\Users\User Name> ipmo oneget-edge
ipmo : The specified module 'oneget-edge' was not loaded because no valid module file was found in any module
directory.
At line:1 char:1
+ ipmo oneget-edge
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (oneget-edge:String) [Import-Module], FileNotFoundExceptio
n
+ FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand
I read Windows 7 may be missing a netframework file. I am gong to try and install that and repeat this.
Nevermind, netframework already installed. I read something about a path. I am trying to figure out how to add a path.
Here is the path and found the module to load.
C:\Program Files (x86)\Outercurve Foundation\OneGet\1.15.82.35272
@groze, Oneget experimental build seems to work just fine in Windows 7, although needing a minute or two to set it up.
Here's what you need to do:
To ugrade PowerShell v. 2 in Windows 7 to v.3, you need to install Dot NET Framework 4 or later. I installed the latest 4.5 from here: Download Microsoft .NET Framework 4.5 from Official Microsoft Download Center
Next, the Windows Management Framework v.3 or later must be installed. For Windows 7 get the v.3 here: Download Windows Management Framework 3.0 from Official Microsoft Download Center. Be sure to select the correct Management Framework, in screenshot below the Windows 7 x64 highlighted with yellow, the x86 with green:Now install the latest OneGet experimental build. When done run PowerShell, it is now upgraded to v.3 showing Copyright notice from 2012 (v.2, the Windows 7 default PowerShell shows 2009) and you can run OneGet.
Here's how I tested OneGet in Windows 7, list item numbers refer to corresponding numbers in the screenshot after the list:
- The Chocolatey package provider where most of the installers come from needs the PS script execution policy to be unrestricted. To change the policy give the following command
The above command applies if you run PS elevated. If not, you need to add parameter -scope with value currentuser to command:Code:set-executionpolicy unrestricted
Code:set-executionpolicy unrestricted -scope currentuser- Next you need to import the OneGet experimental module you installed to the PowerShell. Command is:
(In x86 systems in C:\Program Files\...) Notice that the installer of the module says the command is ipmo oneget-edge but this is wrong, the import module command ipmo needs the full path.Code:ipmo "C:\Program Files (x86)\Outercurve Foundation\OneGet\1.15.82.35272\OneGet-Edge"- By default the package provider Chocolatey is not installed. Get it simply with this command:
Code:get-packageprovider Chocolatey- In my test just now I didn't bother to do anything else, I just went directly to install apps. I gave a OneGet command to install VLC Player, Adobe Reader, Chrome, Screenpresso and WinRAR with command:
Code:install-package VLC, AdobeReader, GoogleChrome, Screenpresso, WinRAR- and 6. VLC, Adobe Reader and Chrome installed OK, Screenpresso and WinRAR which both install OK with OneGet in Windows 10 didn't install. I suspect this is because my test vm was just an x86 system and OneGet retrieved x64 installers for these two apps
Seems to work in Windows 7 :). Notice that as this is an experimental build and not meant to be used in Windows 7, you need to import the OneGet module and get the Chocolatey provider each time you relaunch PS, list items 2 & 3 on the list above.
Kari