xsharp.eu

I converted VO project to X# using VO-xPorter.
Opened the project in visual Studio and changed the Application Dialect to "Core" from "Visual Objects". I tried to build it and get X9019 Compiler option 'vo5'(Implicit CLIPPER calling convention) is not supported for dialect COre error message.
Can you let me know what I need to do to fix this error?

Hi,

Since this is an application that was ported from VO, so it uses things like USUALs, ARRAYs etc, you must keep the Dialect to "Visual Objects", this is the compatibility mode the compiler must be using for compiling such code.

The Core dialect is used only for applications that do not use any VO-specific feature. In case you indeed need to use Core, this error message will go away if you go the Project Properties, "Language" page and set the option "Implicit CLIPPER calling convention" to false. But as I said, most probably you need to use the Visual Objects dialect.

Chris

Thank you Chris.

Now, I am having problem opening xsfrm. I would guess this is the windows/form but when I click on it , it does not do anything.
Do I need any add-on or anything to open this file? If this is not form file then please let me know how to convert the form/windows.

Hi,

Yes, editing VO-style windows is not supported yet, this is one of the features that will follow in the next builds.

Btw, I'm interested to hear your experience with the porting process, did the project that you ported to x# compiled and run, or did you receive error messages?

Chris

I've xported my small VO application and it converted like a magic. Had some errors but that was due to using incorrect VulcanRT.dll and VulcanRTFUncs.dll. Once I changed to use 3.0 version of Vulcan dlls, I was able to compile and run the application.
This is awesome. Thank you so much Chris!!!
We will convert our main application soon. Will keep you posted.

Good day everyone!

I am in the process of moving an application from VO28SP4 to X# and the support on this forum has been fantastic.

VO-xPorter throws the error noted below when importing the AEF.

So, I exported just the MEF and VO-xPorter had no problem.

Any suggestions as to how I could locate the offending "," would be very much appreciated.

Here is a copy of the error:

Thank you!

//----------------------------------------------------------------------------------------------------------------------------------
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Xml.XmlException: The ',' character, hexadecimal value 0x2C, cannot be included in a name.
at System.Xml.XmlDocument.CheckName(String name)
at System.Xml.XmlElement..ctor(XmlName name, Boolean empty, XmlDocument doc)
at System.Xml.XmlDocument.CreateElement(String prefix, String localName, String namespaceURI)
at System.Xml.XmlDocument.CreateElement(String name)
at BinaryEntity.SaveWindowItemToXml(XmlDocument oDocument, VOWEDItem oItem, XmlNode oParentNode)
at BinaryEntity.SaveWindowToXml(String cBinaryFileName, Byte[] aBytes)
at ApplicationDescriptor.Generate()
at VOProjectDescriptor.xPortApps(String cOutputFolder)
at xPorter.xPort_AppFromAef(String cAefFile, String cOutputFolder, String cSolutionName, String cAppName)
at xPorterUI.xPortButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
VOXPorter
Assembly Version: 2.8.0.0
Win32 Version: 2.8.1.12
CodeBase: file:///C:/Program%20Files%20(x86)/XSharp/VOXPorter/VOXporter.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
SDK_Defines
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/XSharp/VOXPorter/SDK_Defines.DLL
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Fab_VO_Entities
Assembly Version: 2.8.0.0
Win32 Version: 2.8.1.12
CodeBase: file:///C:/Program%20Files%20(x86)/XSharp/VOXPorter/Fab_VO_Entities.DLL
----------------------------------------
XIRES
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/XSharp/VOXPorter/XIRES.DLL
----------------------------------------
XICOMMON
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/XSharp/VOXPorter/XICOMMON.DLL
----------------------------------------
XSharp.VODesigners
Assembly Version: 2.8.0.0
Win32 Version: 2.8.1.12
CodeBase: file:///C:/Program%20Files%20(x86)/XSharp/VOXPorter/XSharp.VODesigners.DLL
----------------------------------------
XIDED
Assembly Version: 0.0.0.0
Win32 Version: 0.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/XSharp/VOXPorter/XIDED.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

John, can you please send me the aef, so I can find and fix the problem? If I could make a guess, it must be some window entity with a comma "," inside it's name, or something like that causing the problem. Can you locate such a window? Or a menu, etc.