Rex,

Your question is a little unclear. The Imports command notifies .NET that you are using a particular namespace. It's a little bit like using a WITH...END WITH block to avoid re-typing the complete specification on each object reference. If you are missing Imports commands in your code file, you will see Intellisense errors on the Dim statements (red squiggly underline). If this is the case, add an Imports command that specifies the namespace you created in your DLL.

If your project does not have the proper reference that points to your DLL, you will see Intellisense errors on the Imports command. If you have this error, add a reference to your DLL to the project.

If one of your classes shares a name with a .NET built-in class, you will have to use the complete namespace of your DLL when creating objects based on the DLL.

Dim newObject as new RexNamespace.RexClass()

instead of

Imports RexNamespace
Dim newObject as new RexClass()

Once you have the reference and the Imports command in your code file, .NET will use your DLL anytime you create an object based on the classes in your DLL.

>All,
>
>In my VB.Net application I have removed all the Imports and added them to the project. When I run the application, I keep getting compilation errors saying that the Imports are not there. If I use the project imports, and compile the solution, how do I tell the pages to use the created DLL?
>
>Thanks
>
>Rex