lordmilko/PrtgAPI v0.9.8 on GitHub

PrtgAPI now supports .NET Standard / PowerShell Core! 🎉🎉🎉

PrtgAPI now multi-targets .NET Framework 4.5.2 and .NET Standard 2.0
When installing in PowerShell, PrtgAPI now ships with both .NET Framework and .NET Standard assemblies. .NET Framework assemblies will be used when running on Windows PowerShell, while .NET Standard assemblies will be used on PowerShell Core

PrtgAPI is now SourceLink compatible! Something not working the way you expect it to? You can now step straight into the PrtgAPI source code when developing in Visual Studio 2017+. For more information please see the wiki
Implemented the PrtgAPI Build Environment. All aspects of the PrtgAPI development workflow including dependency management and cross-platform compilation can now be managed via a unified PowerShell module. For more information please see the wiki

GetObjectProperty / Get-ObjectProperty now throws a more appropriate exception message when trying to retrieve "virtual" properties like ObjectProperty.LocationName
Fixed RequestEngine not allowing you to cancel a request while it is waiting to retry using the specified CancellationToken

Updated Get-Help -Online URLs on Get-ObjectProperty, Set-ObjectProperty, Add-Device and Add-Group to reflect wiki organizational changes
Get-ObjectProperty now throws a non-terminating error when a -Property or -RawProperty cannot be found

PowerShell 5.1+ is now mandatory in order to use PrtgAPI. Attempting to import PrtgAPI into a PowerShell version earlier than 5.1 will fail. PrtgAPI previously stated it required PowerShell 5+, so for most people this should not be an issue

Resolved an IQueryable thread safety issue that would sometimes result in PrtgAPI crashing when reading properties from the PropertyEvaluator static property map

Resolved an issue where Set-ObjectProperty did not display -WhatIf and progress messages properly