-
Notifications
You must be signed in to change notification settings - Fork 525
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
paket.exe, paket.bootstrapper.exe don't work behind proxy #226
Comments
is there an SO question or blog post where I can read about that? I'm not sure I know what I have to do to make it work. |
@vasily-kirichenko could you please review/test this? I'm not sure I do the right thing. |
Will do right now. |
Thanks.
|
Where can I find the compiled binary? I cannot build it from sources even with .config files in place. |
|
https://github.com/fsprojects/Paket/releases/tag/0.5.0-alpha008
|
The full log is
|
This is what you binary says
|
I'm trying to fix this. |
Cool. According to
|
Paket itself is build successfully both from command line and inside VS. Great! :) Thanks. I replaced
So we should update Paket version used in VFPT to the latest, but how? |
Try to run paket bootstrapper exe prerelease see
|
Aha. It works :) VFPT is successfully built. Cooool. So, we should replace paket.bootstrapper.exe manually, then use 'prerelease' flag? Oh we should wait when 0.5.0 is released? //cc @dungpa |
I will probabyl release 0.5 today or tomorrow. 2014-10-09 13:50 GMT+02:00 Vasily Kirichenko notifications@github.com:
|
Great. |
It can be fixed by adding
paket.exe.config
andpaket.bootstrapper.exe.config
containingBut it's inconvenient since it cannot be pushed into a public repository.
I suggest to always use default system proxy programmatically for downloading
paket.exe
and nuget packages.The text was updated successfully, but these errors were encountered: