v5.11.1

CHANGELOG.md

@@ -2,6 +2,9 @@
 
 Represents the **NuGet** versions.
 
+## v5.11.1
+- *Fixed:* Wrapped `Assembly.LoadFrom` in `TestSetUp` with try-catch to log exceptions and prevent setup failures.
+
 ## v5.11.0
 - *Enhancement:* Added `AssertorBase.LogMessages` to enable access to the logs captured during execution of the test for assertion purposes. This is intended to be used in conjunction with the existing `ExpectLogContains` expectation to enable additional (more advanced) assertions against the logs.
 

Common.targets

@@ -1,6 +1,6 @@
 <Project>
 	<PropertyGroup>
-		<Version>5.11.0</Version>
+		<Version>5.11.1</Version>
 		<LangVersion>preview</LangVersion>
 		<Authors>Avanade</Authors>
 		<Company>Avanade</Company>

src/UnitTestEx/TestSetUp.cs

@@ -43,7 +43,17 @@ static TestSetUp()
         {
             // Load all dependent assemblies to ensure all one off test set up(s) execute before any test exection is perfomed.
             foreach (var fi in new DirectoryInfo(AppDomain.CurrentDomain.BaseDirectory).EnumerateFiles("*.dll"))
-                Assembly.LoadFrom(fi.FullName);
+            {
+                try
+                {
+                    Assembly.LoadFrom(fi.FullName);
+                }
+                catch (Exception ex)
+                {
+                    // Ignore any load failures; this is not a problem as the assembly may not be relevant to the current test execution.
+                    System.Diagnostics.Debug.WriteLine($"TestSetUp: Unable to load assembly '{fi.FullName}': {ex.Message}");
+                }
+            }
 
             // Wire up for any assemblies already loaded.
             foreach (var assembly in AppDomain.CurrentDomain.GetAssemblies())