I'm doing some extreme tests on the VB6 project. In the test, a VBP project contains thousands of classes and thousands of Interface (classes). In the process of loading VBP, the prompt "Out of memory" appears. So I decide to split this VBP project.
One of the solutions is to put all the interface files (interface classes) into a separate VBP project, and compile this project into an Active-DLL for the main VBP project to call. I'd like to know whether this solution is feasible, and is there a better solution?
Another solution is to put these thousands of interface files (interface classes) in a TLB. I have never created a TLB myself, and I don't know anything about TLB. I don't know if this solution is better.
Any suggestions and hints would be greatly appreciated.
One of the solutions is to put all the interface files (interface classes) into a separate VBP project, and compile this project into an Active-DLL for the main VBP project to call. I'd like to know whether this solution is feasible, and is there a better solution?
Another solution is to put these thousands of interface files (interface classes) in a TLB. I have never created a TLB myself, and I don't know anything about TLB. I don't know if this solution is better.
Any suggestions and hints would be greatly appreciated.