D
dbeavon
Guest
Does anyone have experience with .Net proxygen? There is a wierd little executable that is run during proxygen called "PathFinder.exe" (at C:\Progress\OpenEdge\bin\). It seems to only be used if the compiler option is set up for "default csc" (instead of "custom"). To make a long story short, the "PathFinder.exe" is a bit confused on my machine and it is finding the wrong csc, and not finding xsd.exe at all. Would love to hear if anyone else is using the "default csc" option, and understands the expected behavior of "PathFinder.exe" as it tries to find the paths for compiler tools. Based on the only KB article I could find, Progress KB - Getting error (7246) in proxy log file when generating a .Net proxy from ProxyGen , I'm wondering if it does little more than search the PATH environment variable. It seems to be a pretty unreliable way of locating compiler-related tools. It reminds me of the old "I'm feeling lucky" button in google.
Continue reading...
Continue reading...