views:

29

answers:

0

I have an external DLL file that's needed at runtime. The problem is ASP.NET creates a temporary folder and the DLL gets left behind (see: http://support.dtsearch.com/dts0197.htm). I want to be able to stick this in source control and the next developer to be able to run it.

They suggest using regsvr32, copying the file to the PATH environment variable, or adding the DLL's path to PATH. I don't like any of these solutions because I'm messing with the system, instead of keeping everything encapsulated in the project. Is there a good alternative to handle this?