G
Guest
I have a asp.net application that shares DLL's with some backend vb.net
programs. In my test environment everything works like a champ. When I need a
DLL I point in to the project, do the build and everything works great.
It seems though when I try to move all this to a prod server odd things
happened.
1. if both the online and backend share DLL "x" . "x" exists in the bin
directory where the online component lives and also in the bin dir that
contains the backend vb.net programs. Is this correct? If so when I make a
change to DLL x on my test machine and do I have to copy DLL x to all the
directories that contain DLL x? Is there a way around this ?
programs. In my test environment everything works like a champ. When I need a
DLL I point in to the project, do the build and everything works great.
It seems though when I try to move all this to a prod server odd things
happened.
1. if both the online and backend share DLL "x" . "x" exists in the bin
directory where the online component lives and also in the bin dir that
contains the backend vb.net programs. Is this correct? If so when I make a
change to DLL x on my test machine and do I have to copy DLL x to all the
directories that contain DLL x? Is there a way around this ?