CI: Fix AzDevOps not being recognized as a CI and failing build during zip creation (#4)

Author: JustinGrote

PoshNmap/PoshNmap.psm1

@@ -7,20 +7,16 @@ $AssembliesToLoad = Get-ChildItem -Path "$PSScriptRoot\lib\*-$dotNetTarget.dll"
 if ($AssembliesToLoad) {
     #If we are in a build or a pester test, load assemblies from a temporary file so they don't lock the original file
     #This helps to prevent cleaning problems due to a powershell session locking the file because unloading a module doesn't unload assemblies
-    if ($BuildTask -or $TestDrive) {
+    if ($BuildTask -or $TestDrive -or $env:BUILD_BUILDID) {
         write-verbose "Detected Invoke-Build or Pester, loading assemblies from a temp location to avoid locking issues"
-        <# TODO: Redo this to test for assemblies and if they are in the same path or a temp directory, warn about it. Global vars are bad mmkay.
-        if ($Global:BuildAssembliesLoadedPreviously) {
-            write-warning "You are in a build or test environment. We detected that module assemblies were loaded in this same session on a previous build or test. Strongly recommend you kill the process and start a new session for a clean build/test!"
-        }
-        #>
 
         $TempAssembliesToLoad = @()
         foreach ($AssemblyPathItem in $AssembliesToLoad) {
             $TempAssemblyPath = [System.IO.Path]::GetTempFileName() + ".dll"
             Copy-Item $AssemblyPathItem $TempAssemblyPath
             $TempAssembliesToLoad += [System.IO.FileInfo]$TempAssemblyPath
         }
+
         $AssembliesToLoad = $TempAssembliesToLoad
     }