Screen resources and VO Xporter

semmett · Post by **semmett** » Wed Oct 03, 2018 5:47 am

Sorry, I'm a newbie to X# but been with clipper and VO since the beginning. I know the product still has some limitations and that there are certain runtime libraries that can't be distributed with the product, but I'm trying to understand what can be reused from VO and what can't .

So my first attempt to convert a relatively small exported VO application (.aef) only seems to deal with code. Do I have to recreate the Window resources (screens) again in one of the IDE tools ?

Sorry if this is a basic question, but this is my first real attempt at moving from VO to X# (I abandoned Vulcan after about a week)

Thanks in anticipation.

wriedmann · Post by **wriedmann** » Wed Oct 03, 2018 6:11 am

Hi,

(unfortunately I don't know your name),

are you using XIDE or Visual Studio?
In both the screen ressources should be migrated and it should be possible to extend them.
For XIDE I can assure that because I have migrated a half finished application and I'm continuing the development in X#, as you can see below.

Wolfgang

: voapp_xs.png (90.17 KiB) Viewed 456 times

: xide_voapp.png (76.32 KiB) Viewed 456 times

semmett · Post by **semmett** » Wed Oct 03, 2018 8:05 am

Thank you for your quick reply Wolfgang, and my name is Steve.

I obviously must be doing something wrong and I'll check again when I return home tonight. When is XIDE I thought I would be able to use the import facility but that is expecting a .viaef file and I can't see where one is being generated.

Regards,
Steve

wriedmann · Post by **wriedmann** » Wed Oct 03, 2018 8:50 am

Hi Steve,

if you are migrating from VO, please give a look to this document:

https://www.riedmann.it/download/Migrat ... XSharp.pdf

It should describe how to do an efficient migration (at last from my experience).

Wolfgang

Chris · Post by **Chris** » Wed Oct 03, 2018 11:37 am

Hi Steve,

In short, you need to use the VOXporter tool to export one or more of your aefs (need to your VO apps as .aef files first) in an output folder you will specify. In this folder, you will find a .viproj file, double click on it, tell windows to open such files with XIDE.exe and it will open the project in XIDE.

In order to be able to edit windows and other VO binaries, you will need to also copy the cavowed.inf and .tpl files from your VO bin folder to XIDEConfig. Then you can continue editing them more or like like in VO, do you not have to worry about the resources, they get handled automatically (as in VO).

In order to compile and run the app, for now you will need to have the vulcan runtime. Almost any version would do, so since you did once had briefly used vulcan, please just install it again, simply so that the runtime dlls are available. This will be soon not needed anymore, once we're finished with the x# runtime.

Chris

semmett · Post by **semmett** » Wed Oct 03, 2018 12:49 pm

Thanks Chris, it's this step that I didn't do "In this folder, you will find a .viproj file, double click on it, tell windows to open such files with XIDE.exe and it will open the project in XIDE". I understand the bit about the runtimes and the ini file because I used one of the examples from Wolfgang Riedmann on the wiki and these things were identified in the supporting documents.

A lesson for me is not to try this late at night when you have been been at work for 12 hours, otherwise you can make silly mistakes

Thank you for your help and the help from Wolfgang in pointing me in the right direction, I knew there would be an answer somewhere.

Regards,
Steve

Chris · Post by **Chris** » Wed Oct 03, 2018 4:53 pm

Glad you have it working now Steve! Btw, at some point we need to extend the documentation to make some things more clear...I will write some special notes about importing to XIDE and for how to manage the app from there on.

Main menu