Very Basic VB.Dotnet Deployment Conceptual Questions

[Andy]

Hey All,

I'm a beginner with VB.Dotnet Deployment and I'm a little confused
about some very basic deployment issues . . .

I've now created some core assemblies that will be used throughout all
of our applications that run on various machines on our local network.
I understand that the global assembly cache exists on each machine
where the CLR is installed. But don't I want to establish just one
global assembly cache on say one of our production servers (or some
other relatively secure location that gets backed up routinely) and
just point all of the references to this one location to pick up the
appropriate assemblies? Then when I want to update my core classes
(assemblies) don't I just want to update the assemblies on the
production server (or some other secure location) and just have all
the applications running on all the other machines point to the
assemblies on the production server (or some other secure location)???
If this is true don't I just want to load VB.Net on the production
Server (or some other secure location) and load all my assemblies into
that machine's global assembly cache and then just point my references
to that location from my development machine when I'm writing my
applications? Is this the way to proceed???

I mean the way I see it is that I have a set of core classes
(assemblies) that will be used in all apps running on the individual
machines in the network. So basically I want to house those core
assemblies in one (secure) location, update them when necessary, and
then add code if necessary to my assemblies (I think there are some
configuration settings that I can set that will point to the right
location to pick up the appropriate assembly files) to pick up the
new, updated assemblies in that one, secure location.

Any feedback on these basic issues is very much appreciated . . .

TIA,

Andy