Cancel
Showing results for 
Search instead for 
Did you mean: 

ER: Add ability to use environment variables in assembly load options paths

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Below find an ER of mine, if you find it useful, feel free to ask GTAC to be added to ER#7331962.

                            ER Template
                            -----------

Short Description of desired enhancement: <Problem rather than a solution>
    It is not possible to use a variable like UGII_VERSION in search paths of the assembly load options, to specify version specific search folders for standard parts.

What activity in your process is the product not able to currently handle?
    I want to be able to have one load options file for multiple NX releases, where I can specify version specific search paths.

What result are you trying to achieve? (Please provide as many details as possible.)
    Load standard parts based on the NX release or specify paths using environment variables.

Do you currently have a workaround?
    Use a load options file that contains the version in the file name, like load_options_v8.5.def

Do you have a proposal for the solution you envision Siemens PLM providing for this capability?
    Allow variable expansion as in other configuration files of NX, like using "${MY_FIXTURE_DIR}\${UGII_VERSION}" for search paths.

What is the level of productivity gained from such an enhancement?
    HIGH, easier way to have search paths specified by release or department.

Other information:
Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk Testing: NX12.0 Preparing: NX12.0 | TcVis 11.4

Employees of the customers, together we are strong Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide