Skip to main content

[RESOURCES] : Export components to different pathes

  • October 29, 2024
  • 2 replies
  • 1 view

Ingo Stiller
Forum|alt.badge.img+3

Hi Freaks

In UnifAce 10 we did define  out resource output like this:

[RESOURCES] 
\\\\server\\path\\resources_output

So all components are stored under

\\\\server\\path\\resources_output\\frm

In UnifAce 9 we did this

[FILES]
tst_*.frm    \\\\server\\path\\internal\\frm\\tst_*.frm
int_*.frm    \\\\server\\path\\internal\\frm\\int_*.frm
...
*.frm    \\\\server\\path\\customer\\frm\\tst_*.frm

So internal components stored in

\\\\server\\path\\internal\\frm\\tst_*.frm

and all components that we will deliver in:

\\\\server\\path\\prod\\customer\\tst_*.frm

Is such "switch" also possible in UF 10?

Ingo



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

2 replies

Henk Van der Veer

Hi Freaks

In UnifAce 10 we did define  out resource output like this:

[RESOURCES] 
\\\\server\\path\\resources_output

So all components are stored under

\\\\server\\path\\resources_output\\frm

In UnifAce 9 we did this

[FILES]
tst_*.frm    \\\\server\\path\\internal\\frm\\tst_*.frm
int_*.frm    \\\\server\\path\\internal\\frm\\int_*.frm
...
*.frm    \\\\server\\path\\customer\\frm\\tst_*.frm

So internal components stored in

\\\\server\\path\\internal\\frm\\tst_*.frm

and all components that we will deliver in:

\\\\server\\path\\prod\\customer\\tst_*.frm

Is such "switch" also possible in UF 10?

Ingo



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

Hi Ingo,

Uniface 10 supports  'standardized deployment' only, which means that file redirection for Uniface deployment components is no longer possible.
Actually, the destination for compilation is determined by $resource_output in the [SETTINGS] section. 

The [RESOURCES] section defines where objects are to be found at the time of deployment.

I'm sure you already know, but one way to separate compilation of forms starting with int to a different resource_output target is by using its own dedicated assignment file having its own $resources_output definition.
Simplified:

ide /asn=int.asn /frm int*
ide /asn=tst.asn /frm !int*



------------------------------
Henk Van der Veer
Coöperatie Unividuals Application Management
------------------------------

Ingo Stiller
Forum|alt.badge.img+3
  • Author
  • Participating Frequently
  • 317 replies
  • October 30, 2024

Hi Ingo,

Uniface 10 supports  'standardized deployment' only, which means that file redirection for Uniface deployment components is no longer possible.
Actually, the destination for compilation is determined by $resource_output in the [SETTINGS] section. 

The [RESOURCES] section defines where objects are to be found at the time of deployment.

I'm sure you already know, but one way to separate compilation of forms starting with int to a different resource_output target is by using its own dedicated assignment file having its own $resources_output definition.
Simplified:

ide /asn=int.asn /frm int*
ide /asn=tst.asn /frm !int*



------------------------------
Henk Van der Veer
Coöperatie Unividuals Application Management
------------------------------

Hi Henk

a) I know, and I'm already mourning the good old environments a bit :-)

b) That is a possible way but we have a lot of special cases.
     And once I'm in the IDE, I don't want to worry about how the components are stored.
     The system should solve that in the background

As we need this for our deployment, I have to create a little helper program which moves each component to its proper "pot"

Ingo



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------