JMR
VIP Member
Hey all,
I am not very CNC literate. I am working on an upgrade to 9.2 (TR 9.2.4.1). In my past experience, I swear that checking-in NERs copies the local .h/.c files to their respective folders on the deployment server. Is that correct?
What I am seeing is that is not the case. Is there anything in the OMW/CNC configuration that would dictate this? The c-BSFNs do copy the local .h/.c files just as expected (and necessary). I get that normally this is not a requirement for NERs as those files are generated automatically during package builds. Is this behavior just new to this release/TR?
Just confused and wondering if anybody else has seen this or knows how to configure the system to force that copy.
Thanks.
I am not very CNC literate. I am working on an upgrade to 9.2 (TR 9.2.4.1). In my past experience, I swear that checking-in NERs copies the local .h/.c files to their respective folders on the deployment server. Is that correct?
What I am seeing is that is not the case. Is there anything in the OMW/CNC configuration that would dictate this? The c-BSFNs do copy the local .h/.c files just as expected (and necessary). I get that normally this is not a requirement for NERs as those files are generated automatically during package builds. Is this behavior just new to this release/TR?
Just confused and wondering if anybody else has seen this or knows how to configure the system to force that copy.
Thanks.