Hope the next year is kind to you, and that you start to walk better.
Try to make it to Cologne, Germany, and we can have a chat and a drink. We missed you at the last 'DevShare' event. You can finally meet with Julie my wife, in Cologne. Will your daughter or wife be coming as well?
Thank You Phil,
I am trying to convince my wife to accompany me if I can go, I just have 1 month without using the cane.
I start using the transporter in Vulcan in order to move to x#; but I use report pro 2 (have the source), bbrowser (have the Vulcan version), lots of com with DevExpress and wpf, ADS. At this moment I am using the transporter as the tool to identify problems in my VO code. I am working with many Changes in VO, the time to move to Vulcan and then to x# is not enough.
My goal is to leave VO and move to dot net (x#, c#, wpf).
We have worked on compiling RP 2 and bBrowser this week and found a couple of issues. If you start to convert the RP2 or bBrowser source please contact us, so we can give you the latest compiler and some tips on things that MUST be changed (there are a errors in the source code for both libraries).
XSharp Development Team
I made some corrections before to report pro in order to work with ads.
I did an small app in Vulcan (it is the only one), could not solve the images in the pdf, the program open the pdf and insert the company logo (I'm not happy with this).
Could You share the tips?
Using the transporter to identify problems in your code is a good idea, but I'd suggest not to rely too much on it and definitely not use the modified source that it outputs if you plan to move to X#, because many of the changes that transporter makes, are not needed in X#.
For example, because vulcan only supports double quotes as string delimiters, transporter changes many of your strings to escaped strings. X# supports both single and double quotes as string delimiters, so all those changes are not needed. Same goes for changing the operator to access VOSTRUCT members from "." to ":", changing DEFINEs to #define and more... and soon we will make x# even more compatible with VO code, so in the future even less changes will be required to port your code from VO to X#.
In the coming weeks we will publish a tool that converts VO projects directly to X#, so you will be able to use this one instead.
I don't knew that of the single and double quotes - it is a very welcome addition that makes code more readable specially if you are working with HTML sequences in VO/X# code (very frequent these days - I have more and more notifications and reports that need to be sent out in HTML format).
And regarding the VO system libraries: if many of the changes that the Transporter makes are not needed, then we should wait until the XPorter can do this and use the new tool to move the code ourselves instead of using the Vulcan source code to build the X# version of these libraries?
Yes, I agree single quote string delimiters are very useful, actually it was one of the items in our todo list to bring back in vulcan as well, but obviously we didn't get the chance to implement it there.
As for compiling the SDK, it is up to you, if you want to compile it now, you can simply use the already transported version of the code. Otherwise you can wait till our tool is ready.