Changed: Logic to determine current DLL path, given strange report of…

… failure on user machine.

Source/Reloaded.Assembler/Assembler.cs

@@ -1,4 +1,4 @@
-using System;
+using System;
 using System.Collections.Generic;
 using System.Diagnostics;
 using System.IO;
@@ -199,16 +199,10 @@ private string GetFasmDLLPath()
             throw new FasmWrapperException("Appropriate FASM DLL for X86/64 has not been found in either current or library directory.");
         }
 
-        /// <summary>
-        /// Gets the directory of the currently executing assembly.
-        /// </summary>
-        private string GetExecutingDLLDirectory()
-        {
-            string codeBase = Assembly.GetExecutingAssembly().CodeBase;
-            UriBuilder uri = new UriBuilder(codeBase);
-            string path = Uri.UnescapeDataString(uri.Path);
-            return Path.GetDirectoryName(path);
-        }
+    /// <summary>
+    /// Gets the directory of the currently executing assembly.
+    /// </summary>
+    private string GetExecutingDLLDirectory() => Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location);
 
         /// <summary>
         /// Attempts to allocate the memory to store the text to be supplied to FASM assembler.