use of name: "Object Library" vs. "Class Library"

Hot Topic

how to add new row to dataTable and push the new row to database
Re-loading emails saved by SmtpClient.Send
Can't connect to database from web service!
First call to HttpWebRequest.GetResponse() takes forever and fails, after that it works?
FileStream running slow in Window's forms but not in a windows service
how can we cahce a dataset on the hard drive as we do for asp.net pages
VS 2005 Pro - App. won't run on network drive (W:) - System.TypeInitializationException was unhandled
plugin architecture raises InvalidCastException
Remoting between 32-bit and 64-bit processes?
check SQL Server database/table size

.NET Development

Store Array(list) in Resources?
Excel.PivotTable.SourceData
System.Reflection.ReflectionTypeLoadException
unable to process request -> No connection could be made because the target machine actively refused it.
Assembly not being loaded, ASP.NET
Type of File
Generating DataSet Relations from XML Schema
HTTPListener Speed 25kB/s?
How to dispose all undisposed objects
Multiple Managed Debugging Sessions under one ICorDebugInterface

use of name: "Object Library" vs. "Class Library"

This is a question that I have pondered, but never bothered to really look into it till now. What is the difference between calling library of classes a "Class Library" and an "Object Library"

I've heard these two terms used synonymously, but now I'm at a point where I have to find out if there really is a difference.



Answer this question

use of name: "Object Library" vs. "Class Library"

  • Andrew Todd

    Yeah that would be an object model.

    A "class library" is generally a term used for an assembly which contains the classes (and enums, structs etc).

    An "object model" is the term used to describe how the classes relate to each other, and may involve classes from multiple class libraries.


  • anf600

    In a 'purest' sense you can only have a class library. The class is what defines what an object will be. A class library can (and should) contain many class definitions which are grouped by namespace. You can create a library of classes but you can only create one object at a time. Thus 'Object Library' makes no sense.

  • Paul Diston

    excellent! Thank you


  • sajohnstone

    I understand the difference between a "Class" and an "Object", that's not really what I was getting at with my question. The main reason why I ask, is because my company has partnered with Microsoft on some occasions, and I've heard many developers from Microsoft use both terms synonymously.

    Maybe the reason why I've heard these terms used in this manner is because of our system...

    The system we developed allows a user to create an entire hierarchal collection of objects using a parent/child relationship. Each of these parent objects can contain many child objects. The child objects can contain many child objects, thus becoming the parents of the newly created child objects, and so on. This can go on forever, (great-great-great-great-grandparent, haha).

    Now, in the example I just described, would it be correct to call it an "Object Library"

    EDIT: Or is my example referring to an "Object Model"



  • use of name: "Object Library" vs. "Class Library"
Answer this question