It did give me errors but for only first two includes than execution stopped, nothing happened next. When I removed all the statements except $(Must_Include=..\InitLink.qvs); it worked. I have few questions:
Is there any error count settings for includes, before the script exits?
If InitLink.qvs, resides in the container folder than why do we need to put all the other include lines? Shouldn't the documentation just point where the InitLink.qvs resides in the container and developers will modify their include paths according to it.
And I couldn't find the hidden InitLink.qvs anywhere in the container (it was generated by QDF Tool).
Hi Jawed, It's strange that you can't find the InitLink.qvs that should reside (hidden) in each container base folder? The reason for Cascading includes is that you can move the application up and down in a folder structure without breaking the script. You can not use several cascading must_include as must_Include always break script if url not found.
My suggestion for you is to download the latest QDF version start Deploy Tool and point to the Framework root folder, here you either upgrade or reinitiate the framework depending on your current version (take a backup before). This will update code in all containers as well as the InitLink.qvs file.
Hi Vegar, as InitLink is system/hidden it might not follow if you copy paste content inside a container but it will follow if you copy the container itself. But as long as you have a correct container map it's easy to recover the InltLink using the reinitiation function in Deploy Tool.
Yes, it is strange. I have enabled the option to show the hidden files, but still I can't see it, but I am able to open it in the text editor via the physical location of the file. So InitLink.qvs is there but can't see it in Explorer.
Cascading the includes, I am getting errors but for first two includes than execution stops, nothing happens. Is there any error count settings for cascading includes, before the script exits?