I see, I see. So i guess registering a dll in the GAC wouldn't be accessable no matter what huh? alright, i guess then that com object will have to do. I'm assuming that creating a com dll from a project would be the way to encapsulate some class functionality according to your response. well, thanks once more. I can't seem to find the option to export project to COM, can you give me the path? thanks

Flyin

No, putting a .net dll into the GAC won't help in the COM world. COM can't see the GAC, the GAC is a .net runtime thing.

From a performance standpoint, I'd recommend building a good .net library and then registering it for COM interop. In the project properties, go to "Configuration Properties -> Build". In there is the checkbox for "Register for COM Interop".

Note that you'll be fine when you are running this on the machine you built it on. But when you deploy it, you'll need to use the .net registration tool to register this assembly for COM: C:\WINNT\Microsoft.NET\Framework\v1.1.4322\RegAsm. exe

Peter
------------------------------------------------------
Work smarter, not harder.