exports.conf file

[avianmanagement]

The documentation states:

"in the exports.conf file which can reside in the app and/or the library directory."

I have a aims folder in my thirdparty libs folder

When I create a new app Lianja creates a exports.conf in the app directory

The one in my aims folder has calls to a lot of prgs that I use.

Do I need to delete the exports.conf in the app folder for the app to use the one in the aims folder, or will it use both, i.e. look in one in the apps folder first and if it does not find the entry it will look in the one in the aims folder.

Where exactly and how do I call code so that my apps see the exports.conf in the aims folder in my thirdparty libs folder?

[yvonne.milne]

Hi David,

If an exports.conf file exists in the App, that will be used. If not, it will check for an exports.conf file in the library.

For web Apps, these are checked when the html is generated for the index.html file (and tablet_index.html and phone_index.html). It does not check for an exports.conf file in thirdpartylibs locations.

So you could have an exports.conf that is used by all your Apps, by creating it in the library. In which case, delete the ones in the Apps so that the check for the library one will be done.

If the Apps have the 'Additional file path' attribute set to aims (drive:\lianja\library\thirdpartylibs\aims folder), library files located in that folder (and deployed) and referenced in the exports.conf file (App or library) will be accessible.

Regards,

Yvonne

[avianmanagement]

Thank you.

I'll create a master on in the library file.

Regards


David