Single Class versus Multiple Class DLLs
I have a large order entry type system running IIS using MTX. The COMs are
written using VB6. I wrote the system using a single class module for each
project and then compiled them as DLLs. Each class module contains between
200 and 4000 lines of code. The DLLs are then run under MTX. The system is
working fine, but I always looking to improve matters.
My question is, for an application such as the one I am running, is it better
from an MTX perspective to take the existing single class approach or wrap
all of the class modules into one DLL.
Any thoughts would be appreciated.
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL