Back in v8i any files with the .cfg extension located in the path defined by _USTN_SITE would be read. In CONNECT Edition is there a similar variable that works the same?
# 2) Organization Level
THe organization level basically is what site is in v8i. Any .cfg file in the organization folder will be read.
~HTH
John.
yep
Answer Verified By: Marc Thomas
Hi John
That's the answer I was looking for.
Thanks
Can this be done at the workset level? being at the Organization level doesn't allow for any project specific config files
I don't think that works at Workset level by default.
<quote>Can this be done at the WorkSet level?</quote>
Not by default but can easily be added by placing the following line in your WorkSet.cfg. You can add this at the beginning or end of the cfg to effect the variables before or after. It will process any cfg file in the folder WorkSet name folder.
%if exists ($(_USTN_WORKSETROOT)*.cfg) %include $(_USTN_WORKSETROOT)*.cfg level WorkSet %endif
(edit) The code above isn't needed as it is there by default.
While looking for something else I noticed that they do allow the processing of any cfg file in the WorkSet root folder by default so the code above isn't needed to be added by anyone.
#---------------------------------------------------------------------- # When we get to this point, we have a WorkSet defined. # There may be .cfg files within the WorkSet. Process those here. #---------------------------------------------------------------------- %if exists ($(_USTN_WORKSETROOT)*.cfg) && $(_USTN_HAVEWORKSET) % include $(_USTN_WORKSETROOT)*.cfg level WorkSet %endif
We process *.cfg files in the root folder of Organization, WorkSpace and WorkSet levels.
(For absolute clarity, they're _USTN_ORGANIZATION, _USTN_WORKSPACEROOT and _USTN_WORKSETROOT.)
Marc