Hi all, I have an older Web App that I have built in Xojo 2019 R3.2 that I compile as a standalone Windows executable. I was working on some changes to the app the other day when the power supply in my PC failed. After I got that replaced I was able to load the application okay, however, when I attempt to run it or compile it Xojo gets through the compiling then freezes and becomes unresponsive.
I have tried the following with no joy:
(on my original computer)
tried opening a backup copy
tried clearing the caches
deleting the Debug compile folder
saving the file from binary_xojo_project to just xojo_project
ran chkdsk on my drive
(fired up a new computer with fresh install of Windows 11 and installed Xojo 2019R3.2 and added MBS plugins)
tried opening original file
tried opening backup file
tried clearing caches
tried replacing MBS plugins with latest
tried opening a different project and it loads and compiles just fine.
I assume at this point it is something with the project specifically or possibly some cache that I missed but I cleared the caches manually in the AppData\Roaming\Xojo folder and also clicked the Clear Caches button in the GUI under build settings.
this days i had an issue with windows security, could you exclude the project folder and xojo ide for a test.
if you can compile, is there any output in cmd window if you start it there?
at new pc was there any window asking for network permissions?
the used port is in allowed range?
Well, you’re saying you tried with a backup project; this one couldn’t make the same symptoms if only the original project was corrupted (corruption doesn’t move across projects).
Do both projects share one or more external items?
We do use an EDR application but I checked to be sure that wasn’t the issue. Also, I tried it on a computer with no AV/EDR and still have the same issue so I don’t believe it is that. It has also worked to compile and run it for years before the power issue. In this case I can no longer compile or run the app.
I thought of this after I posted and did remember I had an external item for the MBS license. I also use GraffitiSuite. I replaced both of these with backup copies but that has not fixed it, either.
So I have tried removing the MBS plugins and adding them back in a couple at a time (as my app would complain about missing items). Strangely, one of the first things it complained about was the SQL MBS missing. Once I added it the message (and related messages eg preparedstatement, etc) went away until i had everything added back in. Once all the plugins were back in the directory my app started complaining about the SQL MBS plugins again.
I did discover that I was now able to run and build my application but only as a 32bit application and not 64bit. Any ideas why that would be the case?