View Full Version : Splitting up project file?

Jeff Morse
05-08-2006, 05:07 PM

Our project.uip file is getting to be way too large and cumbersome. We have up to 4 people working the file at a time, and the source code editing & updating process is getting very tiresome. We use ClearCase for our source control where the .uip project file is defined as a text file. We tried the xml file type at first -- the editor/diff/merge tool is easier to use -- but it was taking 30-60 minutes to load up.

Anyway, we're considering breaking up our project file, thinking that it would be easier to work on smaller components and use XSL to recreate the project file at build time. Has anyone else ever done this? Do you have suggestions on the best course of action? I figured we'd at least break the project file into the various sections: Installer.xml, Build.xml, Database.xml, Product.xml & Uninstaller.xml.

Any help and suggestions would be very appreciated.


05-12-2006, 09:01 AM
If you haven't yet, you might look into Collaboration or assemblies to break up the project...

Jeff Morse
05-12-2006, 12:13 PM

Aren't assemblies for assembling multiple individual install projects?


05-12-2006, 12:28 PM
An assembly can also be a standalone product, but doesn't have to be; the Using Advanced Features > Working with Assemblies section of the MultiPlatform help should describe the scenarios better than I can here...

P.S. A superbrief description of the general idea: http://www.macrovision.com/products/flexnet_installshield/multiplatform/features/Collaboration_Design_and_Assemblies.html.