#41 Error importing from assembly that depends on another assemb

closed-fixed
Plugin (17)
5
2010-12-27
2010-09-20
No

I have multiproject solution in .NET 2.0 that has one executable and many libraries. When I try to import the executable I receive the following error:
"System.IO.FileNotFoundException: Could not load file or assembly 'xxx'"

I think that opened assebly file path should be added to AssemblyPath, e.g. when I try to import from C:\projects\xxx\a.exe file the c:\projects\xxx directory should be included in assembly path (note: in .NET 4.0 you have to create new domain to make this work, in .NET 2.0 concatenating the AssemlbyPath should do just fine).

Discussion

  • Malte Ried

    Malte Ried - 2010-12-27

    Hi!

    Thanks for reporting and sorry for the slow response. The bug was somewhat nasty to fix ;) I've implemented a fix and uploaded it to the SVN. The importer now tries to load all *.dll and *.exe files in the directory of the assembly which is imported. So all these assemblies are locked by NClass until it is closed. This will be fixed as soon as possible.

    Malte

     
  • Malte Ried

    Malte Ried - 2010-12-27
    • status: open --> closed-fixed
     

Log in to post a comment.