Tip: using relative paths for dependent ipj's

[ebachrach]

Hi,

Does your ETO project's Inventor project file contains dependent project references?  Are those dependent projects located nested under the primary project in your folder structure?

The ETO project editor, when creating these references, writes hard coded paths in the ipj, because the libraries may not be in nested folders, they could be in some other location altogether.  The result is that anyone else using the ipj must edit those paths to match their own file structure.

However, if the dependent ipj's are in nested locations under the windows directory of the primary project file, you can modify the text of the primary ipj to make those paths relative, so no one setting up your libraries has to edit those paths.

For example, suppose you a primary project file called Application.ipj, and you  have a directory structure relative to the primary ipj as follows:

Application <folder>

     application.ipj

     IntentUIframework <folder>

          IntentUIframework.ipj

     Customer_Generic <folder>

           Customer_Generic.ipj

The dependent libraries node can be written as follows:

            <Dependents>
                 <string>IntentUIFramework\IntentUIFramework.ipj</string>
                <string>Customer_Generic\Customer_Generic.ipj</string>
            </Dependents>

Thanks

Elly