There has to be *something* because COM clients still need CLSID registry
entries (and ProgIDs if you're VBScript) that (typically) point to an
InprocServer32 entry. This will be mscoree.dll for .NET COM servers, and from
then on there's some flexibility, but none of the stuff the COM clients always
needed has gone away. You'll also need to stick to oleautomation parameters if
you've got VBScript clients.

Signature
Phil Wilson [MVP Windows Installer]
----
> I know a .net class can be registered for COM, but can a VB-script use
> CreateObject or GetObject and use a non-registered file location to get the
> object?
>
> Basically, can you call .net from COM directly from the assembly file,
> without registering with com