I would say reflection would be it's own thing. However IAssembly vs IAssemblyName probably makes sense


-----Original Message-----
From: "Aaron Powell" <notifications@github.com>
Sent: ‎5/‎14/‎2013 6:31 PM
To: "scriptcs/scriptcs" <scriptcs@noreply.github.com>
Cc: "Glenn Block" <glenn.block@gmail.com>
Subject: Re: [scriptcs] Non managed dlls (#250)

In src/ScriptCs/Command/ExecuteReplCommand.cs:
> @@ -86,5 +88,18 @@ private IEnumerable<string> GetAssemblyPaths(string workingDirectory)
>  
>              return assemblyPaths;
>          }
> +
> +        private bool IsManagedAssembly(string path)
> +        {
> +            try
> +            {
> +                AssemblyName.GetAssemblyName(path);
Would you want IAssemblyName or a full IAssembly interface so that you could mock out other parts of reflection that'd be important?
—
Reply to this email directly or view it on GitHub.