Page 1 of 1

Interface with .NET framework

Posted: Fri May 26, 2017 3:00 pm
by Rathinagiri
Hi,

Have any of you tried to interface Harbour with .NET framework? I think it may bring new possibilities in various controls.

Re: Interface with .NET framework

Posted: Fri May 26, 2017 3:56 pm
by Anand
I too am keen to know, if it is possible.
HMG + .Net ! WOW !!

Regards,

Anand

Re: Interface with .NET framework

Posted: Fri May 26, 2017 5:20 pm
by serge_girard
No, not yet, but possibilty would be great!

Serge

Re: Interface with .NET framework

Posted: Fri May 26, 2017 9:05 pm
by apais
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 ???????

Re: Interface with .NET framework

Posted: Fri May 26, 2017 9:10 pm
by apais
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 =)

Re: Interface with .NET framework

Posted: Sat May 27, 2017 12:29 am
by Roberto Lopez
apais wrote: Fri May 26, 2017 9:05 pm
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
+1000 :D

Re: Interface with .NET framework

Posted: Sat May 27, 2017 12:30 am
by Roberto Lopez
apais wrote: Fri May 26, 2017 9:10 pm 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 =)
My mental health is not the best and I remember too :)

Re: Interface with .NET framework

Posted: Sat May 27, 2017 12:45 am
by Roberto Lopez
Again...
apais wrote: Fri May 26, 2017 9:05 pm 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
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...