1 source of DLLs for Multiple Servers

Okay, thanks for the info.  I'm sure the videos are great, but I only work part time here, and so I really only have time to look at things directly relevent to the problem at hand.  Also I'm not prepared to invest my personal funds on a work related project, I come here to earn money, not to spend it.

I am currently investigating remoting, and if that doesn't work I'll try web services.

I thought I was using assemblies.  They just seem to have 'dll' extensions, which is why I called them dlls.  Should .net assemblies have different extensions? 

Basically, an example of what I am trying to do, is the database assembly.  This is an assembly that sits on a server with Oracle Client installed, and when called, creates a connection to one of several different database servers we have here.  This mainly gets called by the intranet asp.net application that sits on the same server.

However, there is also another asp.net application that sits on a different server.  This also connects to the same databases, so should use the same assembly.

Also, it is possible that some windows applications may be written that sit on various client machines, that should also reference the same assembly.  This could be especially useful because Oracle Client would not need to be installed on each machine, just the server.

The same thing would apply to other assemblies...

Okay, I have successfully run some tests for both Remoting and Web Services.  I think that Web Services seem a lot cleaner to use than Remoting, although it should be easy enough to just create a Web Services layer that allows access to certain classes to existing classes with the assemblies.

That way the main Intranet application will be able to run directly from the assemblies in its bin, whilst also offering bits of those assemblies to other secondary applications via some Web Services.

As for Oracle drivers, there isn't one with the basic distribution of .Net but MicroSoft have made one available.  I am of course using this, but what I call my Database assembly for accessing our Oracle Databases is higher level code than this.

As for registering dlls etc.  All sounds good although I have no idea what problems there were before because I am an ASP programmer that has only just started using assemblies now we are upgrading to ASP.Net and C#.  That .Net means we can use the same code to write Windows Applications is just something that has opened up possibilities.