This is by design of .NET. It has to do with security. You can setup the .NET assembly to allow it to be called from a network drive, but the steps are pretty convoluted, and, in my experience, not very reliable in terms of actually working. You can check around on MSDN to find out how to allow a .NET component to be accessed remotely.
