Hi,
Have any of you tried to interface Harbour with .NET framework? I think it may bring new possibilities in various controls.
Interface with .NET framework
Moderator: Rathinagiri
- Rathinagiri
- Posts: 5471
- Joined: Tue Jul 29, 2008 6:30 pm
- DBs Used: MariaDB, SQLite, SQLCipher and MySQL
- Location: Sivakasi, India
- Contact:
Interface with .NET framework
East or West HMG is the Best.
South or North HMG is worth.
...the possibilities are endless.
South or North HMG is worth.
...the possibilities are endless.
Re: Interface with .NET framework
I too am keen to know, if it is possible.
HMG + .Net ! WOW !!
Regards,
Anand
HMG + .Net ! WOW !!
Regards,
Anand
- serge_girard
- Posts: 3166
- Joined: Sun Nov 25, 2012 2:44 pm
- DBs Used: 1 MySQL - MariaDB
2 DBF - Location: Belgium
- Contact:
Re: Interface with .NET framework
No, not yet, but possibilty would be great!
Serge
Serge
There's nothing you can do that can't be done...
Re: Interface with .NET framework
harbour = xbase -> pcode -> c code - exec by a virtual machine
.net = c# -> CIL code - exec by a virtual machine
Common Language Infrastructure (CLI) specification and is used by the .NET Framework and Mono
harbour VM size aprox. 1.5mb
.NET Framework VM size > 450 mb
Total incompatibility
Except: COM interface ( active X ) - sometimes problematic because data type serialization issues
SOAP ( web service ) - only for data excchange
PIPES ( available since clipper ) - only for interprocess communications
WM_COPY - only for interprocess communications ( only on same desktop )
The only xbase compiler compatible with CIL is VO (Visual Objects) and in my very humble opinion is abominable.
HTH
Angel
PD: the most viable solution I see for he future of harbour is a traspiler to javascript code so it can be used in browsers and node servers
where is our javascript guru ???????
.net = c# -> CIL code - exec by a virtual machine
Common Language Infrastructure (CLI) specification and is used by the .NET Framework and Mono
harbour VM size aprox. 1.5mb
.NET Framework VM size > 450 mb
Total incompatibility
Except: COM interface ( active X ) - sometimes problematic because data type serialization issues
SOAP ( web service ) - only for data excchange
PIPES ( available since clipper ) - only for interprocess communications
WM_COPY - only for interprocess communications ( only on same desktop )
The only xbase compiler compatible with CIL is VO (Visual Objects) and in my very humble opinion is abominable.
HTH
Angel
PD: the most viable solution I see for he future of harbour is a traspiler to javascript code so it can be used in browsers and node servers
where is our javascript guru ???????
Angel Pais
Web Apps consultant/architect/developer.
Web Apps consultant/architect/developer.
Re: Interface with .NET framework
I still remember very early versions of habour that used to have the choice of generate java code instead of ansi C code.
Or maybe it was a bad dream or my schizophrenia I don't know =)
Or maybe it was a bad dream or my schizophrenia I don't know =)
Angel Pais
Web Apps consultant/architect/developer.
Web Apps consultant/architect/developer.
- Roberto Lopez
- HMG Founder
- Posts: 4004
- Joined: Wed Jul 30, 2008 6:43 pm
- Roberto Lopez
- HMG Founder
- Posts: 4004
- Joined: Wed Jul 30, 2008 6:43 pm
Re: Interface with .NET framework
My mental health is not the best and I remember too
Regards/Saludos,
Roberto
(Veritas Filia Temporis)
Roberto
(Veritas Filia Temporis)
- Roberto Lopez
- HMG Founder
- Posts: 4004
- Joined: Wed Jul 30, 2008 6:43 pm
Re: Interface with .NET framework
Again...
As we already discussed many times, the interest on xBase is constantly declining, so, get enough Javascript expert volunteers to create a development team for 'j-Harbour' could be an impossible mission
So... my hope is that some (syntactic-sugarized) JavaScript variant appear in the future and that via Harbour preprocessor we could create some kind of subset of Harbour for browsers... meanwhile... our world as Harbour programmers is shrinking...
Such thing could require thousands programming hours by a dedicated team of experts.
As we already discussed many times, the interest on xBase is constantly declining, so, get enough Javascript expert volunteers to create a development team for 'j-Harbour' could be an impossible mission
So... my hope is that some (syntactic-sugarized) JavaScript variant appear in the future and that via Harbour preprocessor we could create some kind of subset of Harbour for browsers... meanwhile... our world as Harbour programmers is shrinking...
Regards/Saludos,
Roberto
(Veritas Filia Temporis)
Roberto
(Veritas Filia Temporis)