Hi All,
I've managed to get prolint running on a 10.2B version of Progress but when I follow the exact same instructions and apply it to my 11.5 version of OpenEdge it falls over with "Could not find class or interface org.prorefactor.core.JPNode (12886)." The only major difference between them (other than the version!) is that I run prowin32.exe on version 10.2B and prowin.exe on 11.5. Is there a different version of the proparse dlls for 64 bit systems? Am I missing something obvious?
Thanks,
Mark
Hi Mike,
Thanks loads for the github link, it looks like some good work! I tried replacing the updated assembly files but still no luck. I assume I must be doing something more fundamental wrong, it's strange that in 10.2b my icons seems aware of the assemblies but in 11.5 it doesn't.
Thanks,
Mark
Hi Mike,
Those assembly files did work in the end.. a mistake on my part!
Thanks,
Mark
Hi Mark,
I am also getting that error with 11.4, "Could not find class or interface org.prorefactor.core.JPNode (12886)."
I modified assembly files as suggested by Mike, but still facing the same error in Prolint.p, please let me know what modification you did in order to resolve it.
Thanks in advance.
Ganesh
Hi Ganesh,
Sorry I didn't see this reply as I was away.
I basically just added "-assemblies C:\project\prolint" in the Progress OpenEdge properties startup parameters.
That directory contains the assemblies xml file along with the dlls referenced in that file.
If you've added them correctly you will see "Referenced Assemblies" appear in your project, drill down into that and you should see your 3 new assemblies - where you should be able to view in class browser. Prolint.p should now work fine.
Hope that helps,
Mark
Hi Mark,
Thanks for the info, as you suggested i added assemblies path in OE and it is showing in properties window as well, the issue is i was using Prolint with old assemblies files earlier and now if i am switching to the new files it is showing that error, it is working with old assemblies file though. i am using OE 11.4.
I also checked if somehow old DLLs are registered in my machine (checked in registry), but no luck, not sure where else to look.
Regards,
Ganesh
Does one need to add both the startup parameter under the main Progress OpenEdge page in Project Properties and point to the assemblies.xml file in the Assemblies page?
What is the "default" location on the Assemblies page?
So, other than writing code to use it, is there an easy way to see that the setup is correct and ready to go?
I can't imagine wanting to put it in the working directory.
There seems to be a paucity of set up information other than the guide for installing ProLint, which gives Proparse limited coverage. Am I missing something? I know I did all this with some experiments with Proparse scripting ... but that was like 4 years ago so the details are a little faint.
Well, right, but I haven't written the code yet so I thought I could check that whether I *was* ready to write code.
Right, but the -assemblies piece is pretty simple ... once one has a few bits of information. I seem to remember that there was other setup activities one needed to do to use Proparse.
Hi Mike,
I am using 11.4 (i had 10.2b earlier, i removed it and installed 11.4), now when i am using new assemblies in project it is showing in referenced assemblies but with a cross, also in class browser it shows as (not available), and when i selects it it shows below info -
Assembly IKVM.OpenJDK.Core
Location: IKVM.OpenJDK.Core, Culture=neutral, PublicKeyToken=13235d27fcbfff58
Note:
This assembly is not available to the Class Browser.
The assembly could not be loaded from the global assembly cache or from the assembly directory of the project.
Please suggest.
Finally after some searching, i got it fixed. there is one solution in KB knowledgebase.progress.com/.../000036394, it was for some other issue but similar to my dll loading problem, so i created files as per the solution and its working now.
A few more keywords have been added in release 1117.