Migrate vb.net to Lazarus

[Packs]

I have one application which is written logic part in c# and front end vb.net

Using remoteing.

I would like to migrate to freepascal ui....

But I want to keep c# logic same.

In this project every thing is send through dataset

[cdbc]

Hi
Well, nobody's stopping you from doing that...
AFAIK C# still allows you to create a regular dll, *not* the managed .net kind.
So, stuff all your 'logic' into that /regular/ library and fpc/lazarus will happily call into that library. 
Mind you, the library has to obey C conventions, *not* C# or C++
All you now have to do, is create your visual GUI in lazarus, that relies on your C# backend-library... 
Have fun
Regards Benny

[Packs]

Thank you 🙏.

I am not getting you obey convention in c language means

[Packs]

C# code returning dataset....

How to use same dataset in freepascal.

If I create dll into stand c language type then how to return dataset.

C# function also accept dataset

[cdbc]

Hi
You have to come up with a common data-format, that both C# and FPC understands.
AFAICS Anders took the 'ClientDataset' idea from Delphi and implemented it in C#, 'cause there are a lot of similarities... Then so did we in 'TBufDataset', but being alike is a far cry from being able to talk to or understand each other...
You can try to go the route over the interfaces the C# supports and implement them, to try and talk directly to the 'Dataset-Provider' inside the C# code...
Regards Benny

[cdbc]

...or maybe try ODBC / ADO connections?!?
/bc

[Packs]

In this case I have to modify c# code to make it compatible with Lazarus dataset

[gidesa]

In this case I have to modify c# code to make it compatible with Lazarus dataset

If your application will run on Windows, you can create a C# COM/Activex library.
So you can export quite complex objects, not simple functions as with C API conventions.
Then import the Activex Dll in Lazarus using menu Tools/Import type library.

[Edson]

FAIK there isn't compatible object for the Dataset of .Net in FPC. That's a high level object and don't think can be easily replaced.

I'd suggest to replace the Dataset for a serialized version, maybe a JSON, so you can pass it to the front-end as a simple text.

Every data exchange between the front-end and back-end should be done in a standard format like XML or JSON, due to the incompatibility of the systems.

Thinking more in architecture. I would replace all the back-end in a simple executable file or dll, that should be controlled by the front-end.

[Packs]

You are correct.

It is really big ERP application.

If start to migrate to api it will take time and issues.

So I thought Keep c# I will keep and front end Lazarus.

Or I have migrate to c# front end and use third party component