unitysetup.powershell icon indicating copy to clipboard operation
unitysetup.powershell copied to clipboard

add env variable for installer path for Unity #111

Open abhinuvpitale opened this issue 6 years ago • 5 comments

abhinuvpitale avatar Oct 08 '18 20:10 abhinuvpitale

@jwittner Is this the right way to add the variables?

abhinuvpitale avatar Oct 08 '18 20:10 abhinuvpitale

updated!

abhinuvpitale avatar Oct 09 '18 18:10 abhinuvpitale

After running these commands:

$installers = Find-UnitySetupInstaller -Version 2017.4.8f1 -Components Windows, Vuforia
Install-UnitySetupInstance -Installers $installers

I'm seeing this for my environment variables: environmentannotation

For the version we should actually use $i.Version (which can be seen used further up in the function.)

For the path we should use $destination which will be the install path instead of the package download location.

Ziugy avatar Oct 10 '18 17:10 Ziugy

Not being able to properly setup to test the envir!

abhinuvpitale avatar Oct 13 '18 01:10 abhinuvpitale

What OS are you on? Testing should be as simple as running these three commands from the root of the repository while in PowerShell.

Import-Module .\UnitySetup\UnitySetup.psm1
$installers = Find-UnitySetupInstaller -Version 2017.4.8f1 -Components Windows, Vuforia
Install-UnitySetupInstance -Installers $installers

Visual Studio Code has good debugging options if you need to put breakpoints and step through your code and watch variables. Just make sure to install the PowerShell extension. Should prompt you if you open that file in VS Code.

Ziugy avatar Oct 15 '18 16:10 Ziugy