This topic is locked

Is there documentation for the codebase and structure of the project file

8/4/2016 9:50:51 AM
PHPRunner General questions
P
PHPRunnerExplorer author

Hi,
Is there some existing documentation for the code that PHPRunner generates? It would help, when trying to debug problems.
Also, is there any documentation for the XML structure of the project .phpr files? This could be useful sometimes, e.g., for developing auto-documentation for the PHPRunner-generated applications. This is related to the documentation question by Aleix, at http://www.asprunner.com/forums/topic/20911-documentation-generator/.
The reason I'm asking, is because there were some other CASE tools in the past, that generated Help files with instructions for searching and sorting records, and general data entry tasks.

P
PHPRunnerExplorer author 8/4/2016

I'm moving this to the Suggestion forum, since it's outside the normal scope of php and asp runner.



Hi,
Is there some existing documentation for the code that PHPRunner generates? It would help, when trying to debug problems.
Also, is there any documentation for the XML structure of the project .phpr files? This could be useful sometimes, e.g., for developing auto-documentation for the PHPRunner-generated applications. This is related to the documentation question by Aleix, at http://www.asprunner.com/forums/topic/20911-documentation-generator/.
The reason I'm asking, is because there were some other CASE tools in the past, that generated Help files with instructions for searching and sorting records, and general data entry tasks.

Sergey Kornilov admin 8/4/2016

We do not have the documentation that provides the insight on PHPRunner project file and codebase. These things change fast and also not designed for the end user to tinker with.
If you are try to fix any sort of issue peeking info PHPRunner's generated code you probably doing something wrong. Start by posting the exact issue you dealing with, error messages etc and someone will help you. For instance, in SQL Server connection thread there were no real pointers like error messages till forth message.

P
PHPRunnerExplorer author 8/4/2016

admin,
Actually, I did leave the error message, in the Connection thread:
Fatal error: 18456 [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

18456 [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

in C:\inetpub\selfExclusion\output\connections\MSSQLSrvConnection.php on line 52
That was the 9.0 error message.
In the 8.x version, it was another error that amounted to the same thing. But you're right, I neglected to copy the exact 8.1 error.
In any case, it's always helpful to have some insights and workarounds for a given tool, when things aren't working and nobody is responding. But since it's not practical for PHPRunner to provide documentation on the codebase or project file, I'll just study and get familiarity by trial and error.
Thanks for the response, that should do it for today.



We do not have the documentation that provides the insight on PHPRunner project file and codebase. These things change fast and also not designed for the end user to tinker with.
If you are try to fix any sort of issue peeking info PHPRunner's generated code you probably doing something wrong. Start by posting the exact issue you dealing with, error messages etc and someone will help you. For instance, in SQL Server connection thread there were no real pointers like error messages till forth message.

Sergey Kornilov admin 8/4/2016

What I'm saying is that this error message message did not appear in the thread in question till 4-th post. As soon as I saw the error message I was able to figure out what is going on and provided an insight.
Nobody will be able to help you unless you telling us what exactly is happening. It doesn't matter how deep you dig into the code if you are not telling what exactly is happening. Hope this makes sense. Just trying to explain what kind of info is helpful for troubleshooting.