Hello
I've set up mu projects to keep source and rcode seperately. Each project that depends on another points only to the rcode folder of the other project, not its source.
This gives me tremendous speed advantage when I compile, as all base classes in the stack are not compiled again. I also hope that this will prevents PCT saving the rcode of referenced projects in a shadow folder in the local project, as it can't access the source.
But I cannot run any .Net based screens, because the resx files are not copied to the rcode folder when the file is compiled.
But according to article 000060562, "It was determined that the Progress Product is functioning as designed." and that I must copy the .resx files manually and can log an enhancement request.
So what is the use of a build configuration that results in something that will not run? The moment that I put the source back in the PROPATH, even after the r-code, all the reasons why I made the split in the first place returns and manual processes are prone to failure...
Is this not similar than telling my customers that an income statement and a balance sheet is different and that a year end will move the profit/loss to the retained income account, so it is expected that the balance sheet will be out of balance with the provisional profit or loss for the whole year, it is expected behaviour, that the wotkaround is for them to manually write it in during the year, but "You can log an enhancement request."...
It might be functioning as designed, but that doesn't mean the design was correct...
The split rode and src directories existed before .resx file file support existed. So it wasn't a consideration originally and hence not a design decision originally accounted for. It really ought to be fixed instead of ignored
If something is pre-existing and new functionality is introduced that does not play nice with the pre-existing functionality, it should typically be classified it as a bug, since the design of the new functionality missed something. Why is that not the case here?
I agree that the resx file should be handled by the tool. However for now, there is a simple work around you can try.
You can configure a custom builder to copy the resx files from source to destination easily.
Here is the ant xml that copies resx files from one folder (src) to another folder (bin)
<project name="Resx Handler" default="copy_resx" basedir="."> <target name="copy_resx"> <copy todir="bin"> <fileset dir="src"> <include name="**/*.resx"/> </fileset> </copy> </target> </project>
Save this content to file (lets call it resx_copier.xml).
Right click on the project and select "Properties". In the Properties dialog, select the node called "Builders" - click on "New..." to add a new builder to the project.
Select "Ant Builder" and click Ok. Provide the resx_copier.xml for the Buildfile. Also in the "Targets" tab, for Auto Build, select "Set Targets" and choose "copy_resx"
From now, whenever the project build happens it will invoke the ant task (which will copy the resx file from src to bin).
Hope this is useful.