 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
VB Forum / COM / May 2008are shared dll's on the netword drive a good idea
I have disccovered that there is no technical reason why you cannot register a dll that is on the network. We have a dll that is shared amongst 100 users, only when they are attached to the netword. It defines the ado connection information. Currently we are placing it on c: and registering it there. For the purpose of version control, it would be much easier to have as single copy on the network. What are the reasons I would not want to do this and what is the severity of these reasons? thanks Arnie  SignatureArnie >I have disccovered that there is no technical reason why you cannot register a > dll that is on the network. [quoted text clipped - 6 lines] > What are the reasons I would not want to do this and what is the severity of > these reasons? Makes it a little difficult to update the DLL, as you'd have to wait until it wasn't in use. Signature.NET: It's About Trust! http://vfred.mvps.org I don't think that's a major issue. If we had to change it, we would have to change it for everyone who wanted to go back to work. What about getting hit by 20 - 50 people at once. Would it just slow down a bit, or croak? SignatureArnie > >I have disccovered that there is no technical reason why you cannot register a > > dll that is on the network. [quoted text clipped - 9 lines] > Makes it a little difficult to update the DLL, as you'd have to wait until it wasn't > in use. > I don't think that's a major issue. If we had to change it, we would have to > change it for everyone who wanted to go back to work. That's your call, of course. Somehow, you'll have to get them all to quit your app, do the deed, then tell them they can play again. Depending on the app, it may be easier to just have it autoupdate on startup? > What about getting hit by 20 - 50 people at once. Would it just slow down a > bit, or croak? No difference. The bits are loaded into the client memory at startup, and pretty much stay there. Only speed penalty (probably negligable) will be at the time the DLL is loaded. Signature.NET: It's About Trust! http://vfred.mvps.org Arniec <Arniec@discussions.microsoft.com>'s wild thoughts were released on Wed, 21 May 2008 12:01:02 -0700 bearing the following fruit: >I don't think that's a major issue. If we had to change it, we would have to >change it for everyone who wanted to go back to work. It might not seem like a major issue, but in my experience there are *always* some users who will have the file in use. -- Jan Hyde https://mvp.support.microsoft.com/profile/Jan.Hyde |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.