[Mono-bugs] [Bug 350530] New: AppDomain. ExecuteAssemblyByName produces a file not found error

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=350530


           Summary: AppDomain.ExecuteAssemblyByName produces a file not
                    found error
           Product: Mono: Class Libraries
           Version: 1.2.5
          Platform: i586
        OS/Version: Red Hat 9.0
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at ximian.com
        ReportedBy: coalvilledave at ntlworld.com
         QAContact: mono-bugs at ximian.com
          Found By: Other


Description of Problem:


Steps to reproduce the problem:
1. Create a test assembly which outputs the words "Hello World!"
2. Create another assembly that references this assembly
3. Create a new AppDomain object using AppDomain.Create
4. Call the ExecuteAssemblyByName method on the AppDomain object

Ensure that the referenced assembly is present in the search path

Actual Results:
Unhandled Exception: System.IO.FileNotFoundException: 
  at (wrapper xdomain-invoke) System.AppDomain:ExecuteAssemblyByName (string)
  at (wrapper remoting-invoke-with-check)
System.AppDomain:ExecuteAssemblyByName (string)
  at ApplicationDomainTest.MainClass.Main (System.String[] args) [0x0003c] in
/home/david/Projects/mono/Application Domain Execute Test/Application Domain
Test/Main.cs:17 

Expected Results:
"Hello World!" is output to the console

How often does this happen?
Every time. Please not the ExecuteAssemblyByName method is only available with
net 2.0.

Additional Information: I have attached a monodevelop test solution which
reproduces this error. This is tar'd

The AppDomain.ExecuteAssembly method works as expected. If you change the
method call to this method, and supply a filename rather than the friendly
name, it will work.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.