Printable View
for the lesson here, http://msdn.microsoft.com/en-us/library/ms172603.aspx
i followed everything to the letter, and this is visual studio 2005, but the editor does not recognize the class,
Dim person1 As New persons.persons
the msg is : 'type persons.persons is not defined'
i've checked a lot and all the names look correct to me, must be something simple i've missed?
bob
Thread moved from 'VB6 and Earlier' forum to 'VB.Net' (VB2002 and later) forum
Is the 'persons' class inside a namespace called 'persons'? Have you referenced the classTest project from your form's project?
If you've added the reference correctly then it should work. That said, if you also imported the 'persons' namespace then you'd break it again. If you HAVE imported the 'persons' namespace into your WinForms project then you should be using 'persons' only, not 'persons.persons'.
thanks for the reply, it was a rookie naming issue, when i created the class, i didn't realize it would be recognized, for purposes of identifying the class, by the name given at creation. it used the ide default, classLibrary1, so even tho i had named the project and the .vb, 'persons', it still needs the 'object' name.
so, i'm guessing to keep the class, project, and .vb name all the same?
and also if i make the class into a dll, and add to the components, via component services, the component name will end up being the class name?
bob
I wouldn't necessarily keep the class name the same. You could easily have more than one class in a library, and you certainly couldn't share the name with them, but the other names might as well stay the same to make them easy to keep track of.
just want to get the terminology correct, about the library? and component services
there is the 'class library' that is the ide new project, and there is the component services. is component services considered a library as well? my understanding to make classes accessible to any program/project (they would show in the object browser) you would save them as a dll and then add them to component services?
or alternatively you can add any existing dll to a project in the object browser
what are differences and /or reasons to go the component services route as opposed to adding specific dll's through the object browser?
i'm bracing for being forwarded to a set of 2" thick manuals to answer these questions.
bob