johnfraser
Programmer
I came into my new group about 6 months ago and noticed immediately that there were about 50 versions of the same my1.dll my2.dlls laying around. I successfully put most of the dll's in the gac where they should be for our applications but I'm having trouble with a dll which comes from another location in the company. Associated with it are a number of .jar files that must be located in the same folder as the rest. To make life even more difficult the dll has a factory of sorts that you pass in the assembly path of the dll. I've found a way to reference the path the gac places the file in (it's really obscure and long) but the problem is that the jar files are not there as required.
What is the "best" solution for this? I have a number of options on my plate, some as simple as including all the dll and jar in the project and do a "copy to bin" option on build. It works but then every instance on the server(s) will have to do this.
I've thought of a hard coded path but that isn't good because we don't have immediate access to the server or a gaurenty that they will be installed in the same place every time.
Please your input would be greatly appreciated.
What is the "best" solution for this? I have a number of options on my plate, some as simple as including all the dll and jar in the project and do a "copy to bin" option on build. It works but then every instance on the server(s) will have to do this.
I've thought of a hard coded path but that isn't good because we don't have immediate access to the server or a gaurenty that they will be installed in the same place every time.
Please your input would be greatly appreciated.