>I have a very large EXE (11mb) and would like to break it up so that I can work on one component without affecting others. In other words, I have 5 modules and would like them separate so I can do work on one and recompile my EXE without worrying about where I am on the other 4. Anyone know what I should do?

That depends. It depends on how your project is arranged. For example, an accounting system might have shell, general ledger, accounts payable, accounts receivable, inventory, and production modules. If you have the whole mess thrown together into one project with one class library, one directory with forms, etc... you could have quite a time prying it apart. That said, let me offer a suggestion for arranging your project. Mind you, this is just a "flavors" thing. There are a lot of ways to do this.

In the above example, I would have a "shell" project that was responsible for setting up the operating environment, and keeping track of the global system wide information. Then I could have seperate projects for the different pieces of the system. I would arrange them under a systemic folder structure for development purposes.

D:\MyAccountingSystem
\Shell
\forms
\progs
\libs
\...
\GeneralLedger
\forms
\progs
\libs
\...
\AccountsPayable
\forms
\progs
\libs
\...

You get the idea ... If my project was not quite this big, but I wanted the same type of capability, I would have seperate class libraries for the different modules, different program files, etc... I should point out at this point that most everything I do is in a class library (.VCX), forms, code modules, so forth. I have very little in my projects that isn't in a class library. This makes it easier to move things around if I need to.

Just my 2 krupplenicks worth.

Regards,

Jason