Release 3.0 - #88

Prerequisites

PowerShellGet >= 1.6.0

Necessary for -AllowPrerelease flag on Install-Module.

PS> Install-Module -Name PowerShellGet -Repository PSGallery -Scope CurrentUser -Force -AllowClobber
PS> Remove-Module PowerShellGet
PS> Import-Module PowerShellGet

UnitySetup == 3.0.76-develop

PS> Install-Module -Name UnitySetup -AllowPrerelease -RequiredVersion 3.0.76-develop -Scope CurrentUser -Repository PSGallery

Enhancements

• Adds ability to -ImportPackage via Start-UnityEditor Adds ability to import packages with start-unityeditor #57
• Components are now discovered for existing UnitySetupInstances Components should be discovered for existing UnitySetupInstances #23
• Aliases for common shell commands were added Aliases would really help make some of the common commands simpler #66
  • gusi for Get-UnitySetupInstance
  • gupi for Get-UnityProjectInstance
  • sue for Start-UnityEditor
  • susi for Select-UnitySetupInstance
• Easy conversion to UnitySetupComponent via ConvertTo-UnitySetupComponent
• DSC Resource xUnitySetupInstance for managing Unity installs. A DSC Resource for Unity versions #22

Fixes

• -BuildTarget is now a validated set for Start-UnityEditor. Dev/build target set #56
• The Mac component should now be found on all appropriate versions. Find-UnitySetupInstaller can't find Unity 2017.1.2p3 Mac component #43
• Find-UnitySetupInstaller no longer requires Internet Explorer. Use basic parsing to avoid IE dependency #58
• Installs won't fail due to Examples component. Examples Component Installing Over Unity.exe #60
• Missing versions now properly complain. Start-UnityEditor silently fails with -version with valid format that does not exist #51
• Missing -Component in Find-UnitySetupInstaller now warns. Would be nice to make error handling for missing components better. #54
• UnitySetupInstances installed via the Unity Hub are now correctly discovered. Get-UnitySetupInstance does not find instances of Unity installed via the Unity Hub. #47
• Path for UnitySetupInstance is now the root of the install. The path for UnitySetupInstances should be the install folder #73

Cmdlet Smoke Tests

Please explore the below Cmdlets via help <cmdlet> to attempt to understand them, use them, and report any ideas or issues as issues here on GitHub.

• Find-UnitySetupInstaller
• Get-UnityProjectInstance
• Get-UnitySetupInstance
• Install-UnitySetupInstance
• Select-UnitySetupInstance
• Uninstall-UnitySetupInstance
• Start-UnityEditor
• ConvertTo-UnitySetupComponent

DSC Resource Smoke Tests

Please explore the features of the resource, create a configuration, and apply it to a Local Configuration Manager. Recommend standing up a VM or Container for testing these.

• xUnitySetupInstance