Replacement For The CreateObject("DLLName.ClassName") Method To Be Used In A Terminal Server Environment?

I am in the process of converting vb6 assemblies to VB.NET.I am trying to overcome a particular design challenge.I have a vb6 EXE sitting on a Terminal Server which is shared between multiple customers.Each customer has customizations in the form of overrides to this EXE in custom business logic contained within DLL's.We know what DLL to look at based on a setting in the database.We use the CreateObject ("CustomerDLLName.CustomerClass") method to create late bound objects.If the object is "not nothing", we check for override code.For example, if my base EXE has a sub called PrintForm, based on the logged in user I may use the base sub within the executable, or I may need to use the sub in a custom DLL:

Dim oCustom as Object<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p>

Dim strSetting as String<o:p></o:p>
strSetting = "Customer1DLL.Class1"[code].....

I am struggling to come up with a comparable if not better way to do the same thing in .NET. I want to continue sharing the base EXE so I can't just have separate EXE's and DLL's in separate folders.They all need to live in the same c:/Program Files/[Application Name] root directory so I can take advantage of the Terminal Server's shared application memory.