Hi Johan,
Yes, references in the project to the assemblies from GAC. '
Regards,
Niels
bBrowser.NET migration to X#
- nkristensen
- Posts: 8
- Joined: Sat Feb 24, 2018 6:58 am
- Location: South Africa
bBrowser.NET migration to X#
hi Niels,
strange..... I'm using XIDE to compile, and I have not done anything strange.
Do you are usings Visual Studio or XIDE?
Wolfgang
P.S. I'm using self compiled versions of the VO class libraries, therefore the "strange" name
strange..... I'm using XIDE to compile, and I have not done anything strange.
Do you are usings Visual Studio or XIDE?
Wolfgang
P.S. I'm using self compiled versions of the VO class libraries, therefore the "strange" name
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
- nkristensen
- Posts: 8
- Joined: Sat Feb 24, 2018 6:58 am
- Location: South Africa
bBrowser.NET migration to X#
Thanks Wolfgang,
I am also using XIDE, but I have no complier options set. I will try your settings.
Regards,
Niels
I am also using XIDE, but I have no complier options set. I will try your settings.
Regards,
Niels
- nkristensen
- Posts: 8
- Joined: Sat Feb 24, 2018 6:58 am
- Location: South Africa
bBrowser.NET migration to X#
Wolfgang,
Working now using the same compiler options as you.
Thank you very much to you and Johan.
Regards,
Niels
Working now using the same compiler options as you.
Thank you very much to you and Johan.
Regards,
Niels
bBrowser.NET migration to X#
Hi Niels,
You're welcome!
If you find other difficulties, please drop a note here. I'll try to answer and to add it also to the X# Documentation Project,
Wolfgang
You're welcome!
If you find other difficulties, please drop a note here. I'll try to answer and to add it also to the X# Documentation Project,
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
- lumberjack
- Posts: 727
- Joined: Fri Sep 25, 2015 3:11 pm
- Location: South Africa
bBrowser.NET migration to X#
Hi Niels,
Regards,
You welcome, but the honor goes to Wolfgang. Glad you got it sorted out.nkristensen wrote: Thank you very much to you and Johan.
Regards,
______________________
Johan Nel
Boshof, South Africa
Johan Nel
Boshof, South Africa
- nkristensen
- Posts: 8
- Joined: Sat Feb 24, 2018 6:58 am
- Location: South Africa
bBrowser.NET migration to X#
Sorry to trouble again, but now I am getting:
error XS0426: The type name 'Functions' does not exist in the type 'bBrowser' 6,46 bptrCellGroupMove.prg bBrowser
error XS0426: The type name 'Functions' does not exist in the type 'bBrowser' 6,46 bptrCellGroupMove.prg bBrowser
bBrowser.NET migration to X#
Hi Niels,
strange....do you have applied the same compiler options also to the bBrowser library?
Wolfgang
strange....do you have applied the same compiler options also to the bBrowser library?
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
bBrowser.NET migration to X#
Guys, glad you have all resolved this, without help from us! In general, when you port code from vulcan to X#, you should be using the exact same compiler options in X# that also the vulcan app was using, we have intentionally used the exact same names in the properties pages of VS/XIDE, in order to make this as easy as possible.
Specifically about the "Clipper/Strict" error, the issue is that when you have a method defined as
METHOD Close() // no params or explicit return type
then the compiler does not know if it should be defined as a strongly typed method, or it is a VO-style calling convention method. Using the /vo5 (implicit CLIPPER calling convention) option, tells the compiler to treat such methods as CLIPPER, which is what the rest of the bBrowser code uses.
Chris
Specifically about the "Clipper/Strict" error, the issue is that when you have a method defined as
METHOD Close() // no params or explicit return type
then the compiler does not know if it should be defined as a strongly typed method, or it is a VO-style calling convention method. Using the /vo5 (implicit CLIPPER calling convention) option, tells the compiler to treat such methods as CLIPPER, which is what the rest of the bBrowser code uses.
Chris
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu
bBrowser.NET migration to X#
Hi Niels,
Chris
This is most probably due to a (one of the very few remaining) compiler problem, that you cannot have a class with the same name as the dll. Please check the options for this app, general page, what is the "Assembly Name" option set at? If it's bBrowser, then it will not work correctly, you will need to change it to something different, for example "bBrowserNet". I think the original value there as created by Joachim was "bTools.bBrowser".nkristensen wrote:Sorry to trouble again, but now I am getting:
error XS0426: The type name 'Functions' does not exist in the type 'bBrowser' 6,46 bptrCellGroupMove.prg bBrowser
Chris
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu