You do not register .NET dlls like you would with COM. They are not com components, but rather "managed" components. They don't get registered into the registry.
You can use this new dll from other .NET projects (which is probably what you want to be doing) by adding a reference to it in Visual Studio. The project will automatically copy the dll to the proper directory (bin/debug or bin/release) whenever you do a build, and you'll be able to work with the dll.
There are two common ways to deploy the dlls you create in .NET. One is to place the dll in the same folder as the .exe or other .dlls that are using it. The other is to register it in the GAC (which stands for Global Assembly Cache). For a beginner, the easiest thing to do is simply place the dll into the folder of the app that is using it. Later on, you can learn about using the GAC.
You cannot use this .NET dll directly from VB6 or other applications that use COM (ActiveX) components. To do that, you need to create a Com Callable Wrapper for the component. This is know as COM Interop. This is easy to do, and you can search on how-to for that. If this is what you want to do it is likely that you will also want to install it in the GAC - although you don't have to. You might want to get a bit more experince with .NET before you take this on.
Anyway... thats a start.
Woody Z
http://www.learntoprogramnow.com
Registering a vb.net dll in to the system
