M
Michael.Suarez
Would it be possible to copy the windows/assembly folder to a folder on
a network drive? Then reference the dll's in this folder in a .NET app?
Then treat this folder as a place you can drop any dll that you want to
be shared by several users accross the network.. and deploying updated
dll's would be as simple as dropping them in this folder, and any
future runs of an app referencing the dll would know to use the new
updated one?
If this is possible, how exactly would it be implemented?
If not, why? and is there any way of implementing anything similar?
I pose this idea as a possible solution to my post in the
microsoft.public.dotnet.general forum. Perhaps people were uninterested
in replying due to the length of that post. Needless to say, if you are
interested in any background information, feel free to take a look at
that post as well.
http://groups.google.com/group/micr...4e91e064d13/86f627e283e723da#86f627e283e723da
Otherwise, any feedback on this post alone would be greatly
appreciated.
Thank you.
-Mike
a network drive? Then reference the dll's in this folder in a .NET app?
Then treat this folder as a place you can drop any dll that you want to
be shared by several users accross the network.. and deploying updated
dll's would be as simple as dropping them in this folder, and any
future runs of an app referencing the dll would know to use the new
updated one?
If this is possible, how exactly would it be implemented?
If not, why? and is there any way of implementing anything similar?
I pose this idea as a possible solution to my post in the
microsoft.public.dotnet.general forum. Perhaps people were uninterested
in replying due to the length of that post. Needless to say, if you are
interested in any background information, feel free to take a look at
that post as well.
http://groups.google.com/group/micr...4e91e064d13/86f627e283e723da#86f627e283e723da
Otherwise, any feedback on this post alone would be greatly
appreciated.
Thank you.
-Mike