gsadmin/PSProxmoxVE
1
0
Fork 0
mirror of https://github.com/GoodOlClint/PSProxmoxVE.git synced 2026-08-09 05:49:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(test): load module via .psd1 manifest instead of raw DLL

Browse Source 
Loading via the module manifest (.psd1) ensures PowerShell sets up
proper assembly resolution context. Loading via raw DLL path bypasses
PS's module loading infrastructure and fails on CI runners where the
.NET SDK's assembly resolution conflicts with PS's bundled runtime.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Clint Branham
2026-03-19 08:45:23 -05:00
parent 6871bef77d
commit 7962a549f0
1 changed files with 12 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/PSProxmoxVE.Tests/_TestHelper.ps1
+12 -13
View File
@@ -10,15 +10,14 @@ if (Get-Module -Name PSProxmoxVE) { return }
# 1. Try importing by module name (works in CI where the module is
# installed to a PSModulePath location via dotnet publish + copy).
try {
$available = Get-Module PSProxmoxVE -ListAvailable -ErrorAction SilentlyContinue
if ($available) {
Import-Module PSProxmoxVE -Force -ErrorAction Stop
return
}
catch {
# Module not on PSModulePath — fall through to local-path discovery.
}
# 2. Discover the built DLL from the local source tree.
# 2. Discover the module manifest (.psd1) from the local source tree.
# Loading via manifest ensures PS handles assembly resolution correctly.
# Prefer the framework that matches the running PowerShell edition.
$repoRoot = Resolve-Path (Join-Path $PSScriptRoot '../..')
$moduleRoot = Join-Path $repoRoot 'src/PSProxmoxVE'
@@ -32,21 +31,21 @@ else {
$searchPaths = foreach ($fw in $frameworks) {
# Publish output (has all dependencies co-located)
Join-Path $repoRoot "publish/$fw/PSProxmoxVE.dll"
Join-Path $repoRoot "publish/$fw/PSProxmoxVE.psd1"
# Build output
Join-Path $moduleRoot "bin/Debug/$fw/PSProxmoxVE.dll"
Join-Path $moduleRoot "bin/Release/$fw/PSProxmoxVE.dll"
Join-Path $moduleRoot "bin/Debug/$fw/PSProxmoxVE.psd1"
Join-Path $moduleRoot "bin/Release/$fw/PSProxmoxVE.psd1"
}
$moduleDll = $searchPaths | Where-Object { Test-Path $_ } | Select-Object -First 1
$moduleManifest = $searchPaths | Where-Object { Test-Path $_ } | Select-Object -First 1
if ($null -eq $moduleDll) {
throw "PSProxmoxVE.dll not found. Build the project before running Pester tests."
if ($null -eq $moduleManifest) {
throw "PSProxmoxVE module not found. Build the project before running Pester tests."
}
# Remove deps.json if present — it causes assembly resolution conflicts
# when loading a binary module inside PowerShell's own .NET runtime.
$depsJson = Join-Path (Split-Path $moduleDll) 'PSProxmoxVE.deps.json'
$depsJson = Join-Path (Split-Path $moduleManifest) 'PSProxmoxVE.deps.json'
if (Test-Path $depsJson) { Remove-Item $depsJson -Force }
Import-Module $moduleDll -Force -ErrorAction Stop
Import-Module $moduleManifest -Force -ErrorAction Stop