Skip to content
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

Unable to install dnx (Join-Path $_ "runtimes" failed) #899

Closed
VeselovAndrey opened this issue Sep 7, 2015 · 6 comments
Closed

Unable to install dnx (Join-Path $_ "runtimes" failed) #899

VeselovAndrey opened this issue Sep 7, 2015 · 6 comments
Labels
✔️ Resolution: Duplicate Resolved as a duplicate of another issue

Comments

@VeselovAndrey
Copy link

Unable to install dnx.

 Join-Path : Cannot bind argument to parameter 'Path' because it is an empty string.
 At C:\Users\appveyor\.dnx\bin\dnvm.ps1:207 char:59
 + $RuntimeDirs = $RuntimeHomes | ForEach-Object { Join-Path $_ "runtimes" }
 +                                                           ~~
 + CategoryInfo          : InvalidData: (:) [Join-Path], ParameterBindingValidationException
 + FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand

Full log
https://ci.appveyor.com/project/VeselovAndrey/filewarehouse

@dougbu
Copy link
Member

dougbu commented Sep 7, 2015

/cc @BrennanConroy

If $env:DNX_HOME and $env:DNX_GLOBAL_HOME aren't already defined, $RuntimeHomes is set to ;c:\ProgramData\Microsoft DNX. With that, dnvm.ps1 blows up at the line shown above. A $env:DNX_HOME value wasn't previously required and only a few commands set it.

Side question: When is [Environment]::ExpandEnvironmentVariables($_) required?

@Daniel15
Copy link
Contributor

Daniel15 commented Sep 7, 2015

As a sidenote, if you select "Visual Studio 2015" for AppVeyor's "Operating system" setting, DNVM will be preinstalled and you can just do:

dnvm update-self
dnvm install 1.0.0-beta7

@VeselovAndrey
Copy link
Author

@dougbu Looks like you are right. I have set $env:DNX_HOME and $env:DNX_GLOBAL_HOME manually and install script was completed successfully. But I think install script should be updated to resolve this situation. Thanks.

@Daniel15 Thank. I'm using "Visual Studio 2015" as OS Settings but prefer to keep script as much independent as possible.

@Eneuman
Copy link

Eneuman commented Sep 9, 2015

@VeselovAndrey Can you please share your workaround?
This error also occures when running builds on VSO when you need to install mutiple clrs.

@VeselovAndrey
Copy link
Author

Before install DNX I have added following commands to my PowerShell script:

$env:DNX_HOME="Path to .dnx folder here like C:\Users\yourUserName\.dnx"
$env:DNX_GLOBAL_HOME="same path here"

@dougbu
Copy link
Member

dougbu commented Sep 18, 2015

This is a duplicate of aspnet/dnvm#422. Will track the fix there.

@dougbu dougbu closed this as completed Sep 18, 2015
@Eilon Eilon added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Sep 19, 2015
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
✔️ Resolution: Duplicate Resolved as a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

5 participants