When accessing VB6.0 dlls in classic asp, once the DLL was registered
on the server, you could access that DLL by using a
server.createobject...   It didn't matter where the .dll was
physically located on the server, as long as it was registered.

When trying to access these same VB6.0 dlls from asp.net, if you add a
reference to the dll in the asp.net project, you have to put in the
physical location of the .dll  This causes a problem when you move the
application to another server (i.e. from a development to a production
server) if the dll is physically located at a different path.  Is
there a way to refer to the dll without being concerned about where it
is physically located?  If the DLL is registered, why does it matter
where it is located?  In classic asp, you didn't have to specify the
physical location of the dll.  Is there a way to do this in asp.net?