CODEWITHSUNDEEP
dnxdnvm
Andrew Walters
Andrew Walters

Reputation: 4803

DNX Install - Unable to find any runtime packages on the feed

I'm following this guide on how to get setup with asp.net 5

Running the command dnvm upgrade -r clr from the command line pulls back

Invoke-Command : Unable to find any runtime packages on the feed!
At C:\Program Files\Microsoft DNX\Dnvm\dnvm.ps1:1905 char:23
+         Invoke-Command <<<<  ([ScriptBlock]::Create("dnvm-$cmd $cmdargs"))
    + CategoryInfo          : OperationStopped: (Unable to find ...es on the f
   eed!:String) [Invoke-Command], RuntimeException
    + FullyQualifiedErrorId : Unable to find any runtime packages on the feed!
   ,Microsoft.PowerShell.Commands.InvokeCommandCommand

I've pulled down the latest power shell script from here.

Any thoughts on what I might be missing?

It's something related to proxy authentication, but I'm not sure what needs added where.

Trying to Update DNVM to the latest: enter image description here

enter image description here

Upvotes: 1

Views: 1442

Answers (5)

Naresh MG
Naresh MG

Reputation: 733

I got all kinds of errors (including the one you have mentioned) and were apparently all related to the proxy. setting up the proxy fixed it.

setup either from command line or from the environment variables of your machine

setx http_proxy http::my_proxy_ip_address:port

finding out the combaination of correct ip and port was the biggest challenge for me -;) (and drove me nutts-;)

Did a quick recording while fixing it just in case it helps anyone https://youtu.be/RbYYWS-ZwFY

Upvotes: 0

Fanda
Fanda

Reputation: 3786

I just test latest dnvm.ps1 dev script but default proxy is still not passed automatically. Because I don't want to write my password anywhere, as temporary solutions I have edited dnvm.ps1 script to this (last block of Apply-Proxy method):

function Apply-Proxy {
param(
  [System.Net.WebClient] $wc,
  [string]$Proxy
)
  if (!$Proxy) {
    $Proxy = $env:http_proxy
  }
  if ($Proxy) {
    $wp = New-Object System.Net.WebProxy($Proxy)
    $pb = New-Object UriBuilder($Proxy)
    if (!$pb.UserName) {
        $wp.Credentials = [System.Net.CredentialCache]::DefaultCredentials
    } else {
        $wp.Credentials = New-Object System.Net.NetworkCredential($pb.UserName, $pb.Password)
    }
    $wc.Proxy = $wp
  }
  else {  # edit start
    $wc.Proxy=[System.Net.WebRequest]::DefaultWebProxy;
    $wc.Proxy.Credentials=[System.Net.CredentialCache]::DefaultNetworkCredentials;
  } # edit end
}

And it works. I hope he script will be modified somehow in the future.

Upvotes: 0

John Fouhy
John Fouhy

Reputation: 42203

Try setting the environment variable http_proxy to "server:port".

e.g.

$env:http_proxy='myproxy:8080'

Upvotes: 1

Maxime Rouiller
Maxime Rouiller

Reputation: 13699

This problem has been solved in beta8 scripts.

For now, you'll need to download the script manually and try running it manually.

Since the script is using [System.Net.CredentialCache]::DefaultNetworkCredentials, you might have some chance in setting it in a Powershell Console before invoking the script.

Sample:

[System.Net.CredentialCache]::DefaultNetworkCredentials.Username = "user"
[System.Net.CredentialCache]::DefaultNetworkCredentials.Password = "pwd"
[System.Net.CredentialCache]::DefaultNetworkCredentials.Domain = "domain"

Here's the matching GitHub issue.

Upvotes: 0

Nikola Prokopić
Nikola Prokopić

Reputation: 3496

If you are upgrading behind a proxy server, try adding -Proxy option:

dnvm upgrade -Proxy <server>:<port>

Upvotes: 2

Related Questions