General information
Title:
Splitting up a big exe
Hi guys,
I opened by big mouth in a meeting yesterday and said it would be possible to split up a monolith of an application (17MB exe) into smaller components. The idea was that as various bits of the application change, only the bits that have changed can be updated.
Does anyone have suggestions on the best way to achieve this? I don't want to go all the way to shipping VCXs, SCXs etc compiled outside the app as this would mean too many files to ship. My hope was to be able to break the whole thing up into a dozen files each of 1MB or so.
The app is fairly integrated, and is an 'old-fashioned' design with a main program, large utils program, global variables and forms called with DO FORM from a 'main form'. Classes are generally visible objects/containers dropped onto forms.
Can anyone suggest a way forward? I am open to all ideas!
TIA
Les
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only