Hi Rick,
Low priority observation here as it doesn't appear to be impacting anything I'm doing but when I use FoxBIN2PRG to generate the text equivalent of this VCX, it fails with the following errors:
ERRORS FOUND IN FILE [C:\wconnect\classes\wcvisual.vcx]
* Duplicated Object "commandbutton.requestbrowser.cmdreload" @Recno 30, (1st.Recno:23)
* Duplicated Object "pageframe.requestbrowser.pgfpages" @Recno 26, (1st.Recno:19)
* Duplicated Object "editbox.requestbrowser.pgfpages.pghtml.edthttpresponse" @Recno 27, (1st.Recno:20)
* Duplicated Object "editbox.requestbrowser.pgfpages.pgrawrequest.edthttprawrequest" @Recno 29, (1st.Recno:22)
* Duplicated Object "editbox.requestbrowser.pgfpages.pgrequest.edthttprequest" @Recno 28, (1st.Recno:21)
* Duplicated Object "textbox.requestbrowser.txtstatus" @Recno 31, (1st.Recno:24)
As I've not run into any issues generating text equivalents for other VFP binaries using FoxBIN2PRG, I'm wondering if there's some corruption in the current version of this VCX.
Not sure. Just tried it with my current version and it works for me without errors. Maybe make sure you rebuild and pack, or just replace the wcvisual.vcx
file from the distribution.
+++ Rick ---
Thanks, Rick. I just extracted it from my 7.09 exe and tried creating the text via FB2P and it failed with the same errors. Perhaps my EXE is bad.
Now this does appear to be causing me agita. Has this VCX changed in 7.09? Can I try loading the one from 7.06?
Here's another idea. Can you send me your VC2? Then I can regenerate the binaries from that.
So I used HackCX to delete the duplicate rows and then successfully generate the text file. In the meantime, I've started getting COM access denied messages after building my latest. I'm also seeing a dialog that says:
Property CCODEEDITORCOMMANDLINE is not found.
This appears to be referencing a class in wcvisual. And now I'm back in the whole debug COM permission errors cycle...
Further to this, I'm completely befuddled now. I've been building and deploying updates steadily for the last couple of weeks. Now with the latest build, I can't get it to spin up at all. So I've been going through your troubleshooting bits and I can't even get a fasthit call to work. Here's a (not-so) pretty picture:
This error comes up twice, and after I ignore it the second time it says it can't load wwipstuff.dll
Help and thanks!
COM access denied is normal - you have to run as an administrator to build the project because it includes a COM object which has to be registered in the registry. COM objects register in HKLM and therefore require Admin access.
+++ Rick ---
I sounds like you have some issues in your project. The wwipstuff load error likely is due to the DLL not being found by your project. I'd check and see what your paths are pointing at when you build.
+++ Rick ---
I'm having a hard time to get Foxbin2prg to work at all. It worked a few times but most of the times it simply doesn't seem to do anything. It shows the progress dialog (too brief to read) and then doesn't produce the output file. No error log is generated either - it just silently fails to produce a file. Yet I've produces the vc2
file previously so I don't know WTF is going on with this tool.
I ran it against my distribution build (the one that builds the zip file on the Web site) and I see the same behavior. No errors or duplicates but no output either.
I don't use this tool because for me it has never worked reliably...
+++ Rick ---
So after some more screwing around with the wcvisual.vcx
file in the released version, it seems something there is not working with foxbin2prg
, but it does work with my latest version. Not sure what's different. I hate that foxbin2prg
refuses to give any indication that it didn't work, but it doesn't on the release files. It works on the latest bits though.
This will be fixed in the next release I guess although I have no idea what could be wrong there. Nothing has changed since the release in that file.
You can't use the 7.06
version - there have been changes to the status UI that require this latest build.
+++ Rick ---
I suggest that you report this as an issue, the autor has always been very supportive.
I'm not sure how to report this bug 😃
This is one of those crazy edge cases. I have two versions of the VCX one works one doesn't but they are almost identical. THe one that works just works, the other appears to work but nothing actually gets generated. No Error no failure, no crash, it just doesn't do anything which is kind of scary.
I packed the vcx that didn't work and now it too works, so I don't have the failing file anymore.
+++ Rick ---
If it doesn't fail anymore, then the problems is kind of solved.... 😃 Anyway, if you experience this problem in the future, the author has an "issues" section on github.
It's odd that you don't get an ERR file. In any case, I believe I still have the VCX that misbehaves but I would not forward to Fernando without Rick's permission.
Rick, out of curiosity, how are you invoking FP2B? I've got mine hooked up via a shortcut in the File Explorer Send TO menu like this:
C:\fox\VFPX\Thor\Thor\Tools\Components\FoxBIN2PRG\foxbin2prg.exe "SHOWMSG-BIN2PRG"
I just call it in the FoxPro IDE with a path set into the install folder.
Just what is the behavior you see with the file?
When it wasn't working for me I get no errors - it runs but then no .vc2
was generated.
I've updated the WebConnectionExperiment.zip file with the wcvisual.vcx/vct
that works for me. You can download it from the link.
+++ Rick ---
When I call it via my Send To shortcut, which has that "SHOWMSGS-BIN2PRG" parameter, I always get a messagebox when it finishes. If it's successful I get this:
And when it runs into a problem I get this:
It also pops up Notepad with the ERR file:
(Note the version number in the dialogs. Is is possible that you are running an older version?)
BTW Thor has a nice little plug-in that creates the Send To shortcuts.
I did finally manage to get past the COM permission errors, although I'm still confused as to why it broke in the first place. As mentioned, I've been building and deploying updates for several weeks now. Ultimately, I added the app pool identity, which is a domain account, as a local admin and the COM errors went away. Compounding my fun was an inadvertent back-leveling of the framework to 7.06 via bad Git magic. I think the latter was the root cause of the COM startup errors (property CCODEEDITORCOMMANDLINE not found) while the permissions problem was the cause of wwipstuff.dll not being able to load. Fun...
I'm happy to raise the issue with Fernando but I'll expect he will want a copy of the VCX/T. If you're OK with that, let me know.
So is this working now with the files in the Experimental
zip file?
I'm using the latest version installed with Thor a few days ago.
+++ Rick ---
I hadn't had a chance to try it yet. I will today and will get back to you.
It worked fine and I got the usual confirmation dialog.
BTW should I be using the 2 DLLs from the experimental zip? And since I'm asking silly questions, should I put any WW framework and 3rd party libraries (wwDotNetBridge, wwIPStuff, etc) in the bin folder in the web server environment or in the same folder as the EXE?