Thanks Cathi, worked like a charm!

And yes, the weather is a bit on the cold side, but typical February weather. :) Have a great day!

>Hi Eric,
>
>Are you experiencing any of that bad weather I'm hearing about on the East Coast??
>
>As far as adding you DLL to the .NET Components list, to display your assembly in the Add Reference dialog box, you can add a registry key, such as the following, which points to the location of the assembly
>[HKEY_CURRENT_USER\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders\MyAssemblies]@="C:\\MyAssemblies"
>
>where MyAssemblies is the name of the folder in which the assemblies reside.
>
>NOTE: You can create the this registry entry under the HKEY_LOCAL_MACHINE hive. This will change the setting for all of the users on the system. If you create this registry entry under HKEY_CURRENT_USER, this entry will affect the setting for only the current user.
>
>Restart Visual Studio .NET after you have added the key.
>
>
>>Good day everyone!
>>
>>When you add a reference to a .Net component, you can go to References and add a reference. Then the dialog box comes up where you can pick .Net, COM, or you own projects as a reference component. I have a .Net control that I created that I want my colleagues to use. How can I get my control to show up in the .Net component list instead of them having to browse for the DLL all the time? Is there a certain way to make the deployment project or is this something that cannot be done? I thank you all for your time and assistance.
>>
>>Thanks!