Hi Jacci!

Having fun? <g> The difference is this ... the Imports is a namespace thing and makes it easier for typing so that you don't have to put the complete namespace for an object. For instance, if you have Imports System.Windows.Form, then when adding a TextBox, you can just say TextBox instead of having to fully qualify it. The references is a compiler thing ... so that the compiler knows where to find your namespaces.

~~Bonnie



>Hi All,
>
>I'm currently taking a MS class "Programming With the MS .Net Framework with VB". The class is a little deeper than I expected.
>
>I'm really new to the whole VB arena. An issue has come up that maybe someone here can explain. Why is it that just listing a class library in the References tab of the project isn't enough that sometimes you have to use the Imports at the top of the file?
>
>For instance we are going over serialization and just adding the following statement isn't enough:
>
>Imports System.Runtime.Serialization.Formatters.Soap
>
>A reference to this also has to be added to the project before the SoapFormatter is recognized.
>
>TIA,
>Jacci