Error Loading the File: Open failed

[jay_dee]

Hi,
My App Dev program is throwing an "open fialed" error message with any App Dev program created in the last month or so.
It will still open files made back in 2022.
I have recently run a full update on FC10, and the embedded side is working fine.
My App Dev program reports it is version V9.3.1.36 Nov 02 2022

I'm guessing it is a version issue, i have restarted the PC etc.. but problem persists.
Appologies if this is me being dumb. J.

[medelec35]

hi J.
When there is a new version of Flowcode, PC developer runtime files are also updated to match.
If therefore if you are developing PC developer app, and using an updated version of Flowcode
When you use Deploy as Flowcode APP, then make sure Bundle App Developer Runtime is selected.

[jay_dee]

Thanks Martin,
So this looks like a windows cockup. It has assocaited all APP Dev program files to the older version of App Dev.
If I direcly run the App Dev runtime in the new projects folder, everything is fine.
But if i directly click on a deployed App Dev project, windows will try doing to with the old version.

Unfortunatly Windows wont allow me to associate the App Dev project files to the latest version of Runtime.
Mostly because Windows is now a novelty OS writen in crayon and wont let you associate to anything that is not from the windows store or declared as 'installed'.
I can Pin the latest App Dev runtime to the start menu so this is a reasonable workaround.
Thanks for your help. J.

[medelec35]

You should not need to reassociate, you can select Bundle App Developer Runtime when deploying, or just copy App developer folder from Flowcode v10 installation folder and paste as the new App Developer folder for all your PC developer apps.

[jay_dee]

Thanks Martin,
Yes I always Bundle App Dev. The deployed package works fine.
I now have a shortcut from my start menu to the latest runtime in the FC10 folder, this work fine.

No big issue, it is just when I double click an associated raw app dev file .mscada, window has associated this file with the older runtime. hey ho.

[medelec35]

Ah yes, I understand
When I had that issue when updating a new exe file, in say location A, when I added an updated exe to location B, windows would not assign to version B, it always reverted to version A.
The only way I could get it to assign to location B is to rename the exe in location A, so windows can't find it.
If you can delete or rename the file that windows originally associated with then maybe then you can associate with the new version