views:

709

answers:

4

I have a class library that uses some xml files found in its own directory.

When referencing this library from another project, how do I ensure the library is working from it's own directory?

I tried Assembly.GetExecutingAssembly().Location but that still returns the path of the startup project.

A: 

I don't think you can unless you start it in a new AppDomain, and that's more trouble than it's worth. Just copy the files it needs into your own project, and put them in the place it expects relative to your working directory.

(You might also want to ask the original developer why the paths to the needed files can't be given as a parameter. This would be the normal way of solving this problem.)

Mark Byers
I am the original developer so this might be an option but I don't want to have to keep a seperate copy of the same xml files for each project that uses the library.
Daniel Skinner
A: 

I'm sure there is some functions to get the list of loaded assemblies from the ExecutingAssembly, loop across this to find you assemble(class lib) then get it's location. Sorry for vague answer.

Simeon Pilgrim
+4  A: 

This is happening because your startup project has two options as to loading the library

  1. Copy it to it's own folder (what would cause the behaviour you are experimenting)
  2. Load it from GAC (what would make impossible to load any XML from it's folder)

So you have two options here:

  1. Import the XML files in the project and embed them as "embedded resources" in the class library and load it in memory at runtime
  2. Import the XML files in the project and change the "copy to output directory" property of the file to "true".
Ciwee
Point 2 worked. However, it doesn't seem an ideal solution since there could be clashes. The reason it wasn't working before is because I also had a Data directory in another referenced project.
Daniel Skinner
Use option 1 instead so.. but application users won't be able to edit the XMLs. I can't see other options.
Ciwee
To add another options: Put the XML files into some designated data directory and store that directory path in your app.config. After you, you *will* deploy your project to other PCs and use it outside of Visual Studio, won't you?
Heinzi
A: 

I know this is an old post but in the event someone else stumbles on it from a search, the easiest way I've found to do this is:

Public Class Foo

     Public Shared Function GetMyPath() As String
          Return Path.GetDirectoryName(GetType(Foo).Assembly.Location)
     End Function

End Class
Lance