How many classes can a dll contain

Net DLL can contain any no of classes and each class can contain number of methords and properties as well All classes which are in a DLL can kept into one Namespace when you add a referenc to this DLL into your project and create a new object all classes and methord you can you it as you like Is This Answer Correct?

More ASP. NET Interview Questions. How does asp net store session ids by default? Master Property? For more ASP. Read the question carefully. In can be well interpreted as "How many classes a single DLL library can contain? The only problem is the inaccurate mentioning of "DLL library". I explained it in my answer, please see. I did read the question very carefully. The question as written is "how many classes can contain a single dll library".

The correct and only answer to that question is zero. It is not up to me to interpret the questions. I answered the question as written. I don't blame you Accept Solution Reject Solution. There is no such limitation. And a library does not mean DLL. Essentially, in. The central notion is the assembly. There could be more then one module in one assembly don't mix up modules with referenced assemblies , but Visual Studio only support single-mode assemblies. It is not.

Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search. Not sure what the question is? Classes are definitions that get compiled into the DLL that your projects can reference, I don't think there is a limit as to the number of classes By default, all of your ASP.

Net code will compile into a single DLL, which is typically named after the application in question. However, if you need multiple classes to provide support for your data access layer, or custom objects, your best bet is to create a solution in Visual Studio with multiple projects.

A class library for your data access layer, and a class library for each of your custom objects. From there you can simply add a reference to each of your custom libraries from within your ASP. Net application and the web application will pull in the updated DLLs as needed. There is no documented limit that I've seen for the number of classes a DLL can contain. My guess would be that there is a point where you might have so many classes in a DLL that some operations would be slow or may crash due to out of memory or stack overflow exceptions.

MapPath do? Name atleast three methods of response object other than Redirect. Name atleast two methods of response object other than Transfer. What is State? How many types of cookies are there? How to find the SQL server version from Query Analyser Using query analyzer, name 3 ways you can get an accurate count of the number of records in a table.

What is one of the first things you would do to increase performance of a query? What is an execution plan? When would you use it? How would you view the execution plan? What are the implications of having it off? What is the difference between a Local temporary table and a Global temporary table? How is each one used? What are cursors? Name four type of cursors and when each one would be applied? What is referential integrity and how can we achieve it?

What is indexing? Explain differences between server. What is de-normalization? When do you do it and how? What is DataWarehousing? What is OLAP?