Wolfgang, Your code works very well. I added the following to the Start() function and the error is caught and shown correctly nExitCode := 1/nExitCode An unhandled exception has occurred =================================== Exception: Attempted to divide by zero. Callstack: at Functions.Start() in C ...

Karl,

'a' is a local variable. This variable is not accessible in a macro.
To solve this you can:
- make 'a' a global variable
- make 'a' a dynamic variable (public or private). You will have to enable support for memory variables in the compiler options for this.

Robert

Wolfgang, The executable is "DictEdit.exe", and therefore I would assume the fully specified entry point class name is "DictEdit.Exe.XStartupCode". That is an incorrect assumption. The only namespace that is derived from the assembly name is the namespace from the Functions class. Your own classes ...

Wolfgang, When you migrate a VO app with the name DictEdit, then the generated Assembly name by the Exporter is DictEdit.EXE and the Default Namespace is also DictEdit Please note that this default namespace is only used with: - when you enable the option "Prefix classes with Default Namespace". In ...

People,
I'll contact Joachims company to find out what's happening.
If they no longer wish to support bBrowser, then we'll adopt it, like we have also done for ReportPro

Robert

Guys, There are 3 versions of TEXT .. ENDTEXT. There is one version for the Core dialect: TEXT TO <VariableName> [ADDITIVE] TextLines ENDTEXT This does need any runtime support. There a version for all other dialects except FoxPro TEXT [INTO <VariableName> [TRIMMED]] | [INTO <VariableName> WRAP ...

Guys, Just to be clear: this will not be the first Xbase++ application running in X#. In the Netherlands a fairly large Xbase++ is running in X#. However, this app did not use the Xbase++ GUI classes. It is basically a console app that runs as backend for a web app and processes a lot of data. To ...

Radim,

I agree with Johan.
And also: private email support is for subscribers only.

Robert

The Hyperlabel class expects a Symbol as first parameter. So Hyperlabel{ #DoSomething(cFile,.T.) is not allowed. If you want to pass parameters to the method, I recommend that you create a parameter less event handler, and call the method from that event handler self:RegisterItem( nID, Hyperlabel ...

John,
Thanks for the report.
It looks like Microsoft has changed something without notifying the 3rd party.
I'll take a look at this.

Robert