It's all about the answers!

Ask a question

Load... vs Load As...


Danil Suits (81177) | asked Jul 12 '10, 4:29 p.m.
One of my team just got crossed up by using Load As... where Load... does what he wanted.

Besides the changes in the folder structure on the disk, are there other real differences between the two?

When is appropriate to Load As... a component rather than loading it?

Does a single developer working on a project normally use more than one mechanism to load a component? Does a team always use a uniform approach to loading components?

One answer



permanent link
Geoffrey Clemm (30.1k33035) | answered Jul 12 '10, 7:40 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You can think of "Load As" as just an advanced form of "Load" that
allows you to explicitly control the location to which the files get
loaded ("Load" just loads them into a default place). In the "Load As"
wizard, that initial value for that location is the location used by the
"Load" wizard.

As to whether a developer ever needs to use "Load As" ... that depends
on whether you (or more commonly, your build system) requires that files
be loaded somewhere other than the default place where they are loaded
by RTC.

Cheers,
Geoff

On 7/12/2010 4:36 PM, Danil wrote:
One of my team just got crossed up by using Load As... where Load...
does what he wanted.

Besides the changes in the folder structure on the disk, are there
other real differences between the two?

When is appropriate to Load As... a component rather than loading it?

Does a single developer working on a project normally use more than
one mechanism to load a component? Does a team always use a uniform
approach to loading components?

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.