7.0.36

Changes:

• b9413e1 Merge pull request #9 from AITGmbH/Features/v7ReleasePrep
• b393157 Support for loading older hyper-v powershell modules
• d0d11a1 task variable name changed for timeout handling of app healthy start vm ( advanced behaviour
• 002e17a Bugfix for "VisibleRule for StartVM was only visible if the action value has been changed"
• ee7479a Changed issue link to github issues, added additional tags, fixed screenshot links in extension manifest
• aa8c05b Additional output for VMs are already turned off
• 6e3e683 Fixed "endless" loop in stop-vmturnoffvm
• 938c763 Bugfix in turnoff action (for loop)
• a6f3d77 PSScriptAnalyser disabled because task hangs at end of execution
• f421ae7 Updated descriptions in differnt json and markup files, renamed action stopvm to shutdownvm and added direct turn off of vms

See More

• 7af7662 Fixed bug in new time based check (StartVM action), Improved build task messages in check status functions (StartVM action), removed useless "dead" code
• 6c7d53b Increased logging of some internal control variables, bugfix for time-based status check
• ecff176 Additional status checks after starting VMs and small bugfixes
• 66ec315 Fixed SyntaxError: Unexpected token ] in JSON at position 3045
• 3094fc0 Work on additional status checks for starting VMs continued, manifest adapted to new status check property
• 35d0b84 Started work on additonal status check types -> Time-based status check for stating vms; as part of this effort some parts of the existing logic have been refactored
• c23225c Improved instructions for Build Agent user permissions -> a group was missing (Remote Management Users)
• 20f9c74 Replaced setting hyper-v permission via adsi with net localgroup
• 7728134 Merge pull request #7 from AITGmbH/features/FixPSScriptAnalyzerError
• 079a1de Replaces community analyzer rules with out-of-the-box rules because the latest release of psscriptanalyzer throws an exception, removed some trailing whitespaces (rules violation)
• fcb093c Added latest version of communityanalyzerrules from https://github.com/PowerShell/PSScriptAnalyzer
• da4c672 Still trying to figure out why psscriptanalyzer throws an exception during analysis
• e62aae1 Test fix for psscriptanalyzer rule exception
• ed6788a Additional adjustments for PowershellHandler3 made -> variable handling works differently under 3
• 18016b6 Add VstsTaskSdk PowerShell SDK during build
• 56d89fb Fix for issue #4, hyper-v hostname was missing in vmeventing calls
• 28cf7f1 Added RM release badges to repo readme
• d7ff9cb Merge pull request #3 from AITGmbH/features/CommunityAnalyzerRules
• 4f8799e Added help comments because latest change introduced new rules violations (CommunityAnalyzerRules\Measure-HelpNote)
• cf52cf2 Merge branch 'master' into features/CommunityAnalyzerRules
• 35124a5 Added VSCode launch file to make local testing of powershell functions a little bit easier
• a192ffb Increased version to 7 because of moving to Powershell3 execution handler
• 70eda6d shouldprocess for function Restore-HyperVSnapshot implemented so that all functions are built consistently
• 04b95a2 Create CONTRIBUTING.md
• 34986fe Create LICENSE
• fc48e63 Confirm our own functions with yes (shouldprocess)
• dfddbd6 Refactored and improved powershell code based on PSScriptAnalyzer output -> e.g. ShouldProcess, PSUseSingularNouns, PSAvoidUsingWMICmdlet
• bb5f1c4 Added PSScriptAnalyzer task with some specific rule exclusions to yaml based buld definition
• 3992108 Added PowerShell PSScriptAnalyzer rules from https://github.com/PowerShell/PSScriptAnalyzer/tree/development/Tests/Engine/CommunityAnalyzerRules
• 12162e3 Update README.md
• aa0a124 Update README.md
• da0a322 Update README.md

This list of changes was auto generated.