Should we push this to chocolatey during the build?

I think so. That is what I do for SourceLink.exe. You could also do that same for paket.

cool. It's uploaded to https://chocolatey.org/packages/Paket.PowerShell/1.14.0, but await moderator approval.

I'm pretty sure Paket's release cycle will annoy the hell out of the choco guys.

After the installation, it cannot be used in the PS console, like path is not added.

@alexeyzimarev Are you trying to use it from the Package Manager Console in Visual Studio? Are you able to use it from normal PowerShell? It worked for me with this simple test:

Did the path get added correctly to the PSModulePath?

(Get-Item Env:\PSModulePath).Value -Split ';'

The PSModulePath allows the module to be imported on demand. If that is not working, are you ale to import it manually?

Import-Module C:\ProgramData\chocolatey\lib\Paket.PowerShell\tools\Paket.PowerShell\Paket.PowerShell.dll -DisableNameChecking

@alexeyzimarev It looks like some output doesn't show up. Is that what you mean? I logged this bug and will look into it. #874

No, for me it was just saying that "Paket" is not a valid command. I tried from the PS shell. Will check the path later.

This is what I got after cinst

PS D:\GitHub\Paket.VisualStudio> (Get-Item Env:\PSModulePath).Value -Split ';'
C:\Windows\system32\WindowsPowerShell\v1.0\Modules
C:\Program Files (x86)\Microsoft SQL Server\120\Tools\PowerShell\Modules\

Import gives this:

Hi @alexeyzimarev, I'm not sure why you get that error message. Can you provide the output of these commands?

$PSVersionTable
choco --version
choco list --localonly
Get-FileHash C:\ProgramData\chocolatey\lib\Paket.PowerShell\tools\Paket.PowerShell\Paket.PowerShell.dll -Algorithm SHA1 | fl

Unless I coded something wrong, C:\ProgramData\chocolatey\lib\Paket.PowerShell\tools should get added to your $PSModulePath. I've tested it on a couple of computers. Start a new PowerShell session after installing.

• https://github.com/fsprojects/Paket/blob/master/src/Paket.PowerShell/Install-PSModulePath.ps1
• adds helpers/functions/Install-PSModulePath.ps1 chocolatey/choco#327

@alexeyzimarev did you close and reopen your shell?

So forcing the import worked for me.

I did notice that you are adding a bunch of unapproved verbs, which might be why it didn't automatically import?

This might be helpful as well.

Dumb question. Does a module automatically load without a psd1/psm1 file?

Actually the dumbest possibility, did you need the trailing back slash at the end of your custom module path? http://stackoverflow.com/a/23942543/18475

@ferventcoder There is not a Paket command. If you open a new PowerShell instance and type Paket- or just pak and hit tab, do you see a list? PowerShell will import it as soon as you try running one of them. If so, the $env:psmodulepath is doing its job. I've now tried successfully on 3 computers.

I didn't, but this may be helpful

WMF 5 by the way. I added the trailing back slash and

Seems to work without the trailing backslash as well. With Paket- {tab}

so should be good to approve. :)

Approved.

With the project owners building the package, we move things to a trusted status after a few good approvals @forki.

Awesome! Thank you! Sometime this week, I hope to get a blog about how I used F# Chocolatey PowerShell. :-)

:)