xsharp.eu

Hi Wolfgang,

Oz? that was odd! <g>

I think you are talking about Hey Phil (Phil McGuiness aka Sherlock). We have some exchanges before and probably, If my memory serve me well, some X# guys made some "concept" about this stuff too. Maybe he was author of some VO2RDD (I still cannot remember his name, but he is bz with X# Runtime anyway).

kidding aside, I am ready to pay (must be affordable) anyone that can provide me a transition from ADS to PostgreSQL with ADO.NET. Of course, I am ready to make some serious re-coding as navigational and set based (SQL) are poles apart. I can live with forward only datareader, but I need plug-in replacement of dbserver and grow from there. May I know that guy in Italy that do some RDD for MySQL? Maybe, I heard about him a bit, but I am not MySQL shop.

Regards,

Rene

Wolfgang Riedmann wrote:Hi Rene,

there was a guy from Australia, I think that some time ago wrote he had a RDD for PostgreSQL. I had asked more than one time, and of course I would have paid for such a tool, but haven't received any answer.

I know other people here in Italy is working on a VO RDD to MySQL.

Wolfgang

Hi Rene,

yes, if I remember correctly, it was Phil McGuiness that wrote about a PostgreSQL DataServer (not RDD). But unfortunately he could not answer.

The work on the MySQL RDD is done by Alessandro Vacchiano, based on the original work of Antonello Negrone (that has done also a client/server RDD in Visual Objects).

AFAIK this RDD is not yet finished, and one of my programmers had done also some work on it.

Wolfgang

Hi Wolfgang,

On Italian MySQL gang: I am not surprised that some of the names are very familiar to me.

Maybe someday (within a year) I have clearer picture on my next devt phase. For now, my concern is to get my schedule up to speed and resume X# porting process. I stop last time due to tight schedule as I need more time to allocate in testing X# apps maybe more than the porting process.

After that, I will seriously work on RDD replacement for PostgreSQL using ADO.NET with paid third party .net connector for PostgreSQL which all our stuff (MVC and cloud) are using.

Regards,

Rene

Hi Rene,

regarding VO migration: today I was able to run the first time one of my VO applications compiled with X# - it is a middle sized application that uses ADS and DBF, and consist of 90.000 lines of code not counting my framework libraries. The VO exe has a size of 11 MB.
Currently some windows are crashing, and I need to port my printing library, but only to be able to run this application is an important milestone for me.

Wolfgang

Hi Wolfgang,

that is wow!

I wish I could allocate time to X# migration. But anyway, I am using X# in the ADS to PostgreSQL replication, my primary purpose in joining FOX, secondary is porting process of our very big banking apps. I cannot count the number of forms, late bound calls, customized timers, DLL loading, bBrowser grid, RP3/CM200 codes, Fabs (all of it), and many more (strict, pascal, clipper calling convention). Calling it off for the mean is a good call because it could push our schedules further. Porting process need to be done when no one is waiting. Haste make waste!

Regards,

Rene

Hi Rene,

I have no time too.... Seems I'm one of the guys that is never able to accomplish all what customers are expecting. Therefore I take my time by hours - sometimes when I'm locked in some problem, I start working on the migration, and so step by step I'm arrived at this point, but several things remain to do before I can put this program in production (should be matter of weeks, not of months).
Until the migration is complete, my VO code remains compatible to the X# version, and I'm working heavily with #ifdef like these:
Wolfgang

Hi Wolfgang,

Is your code compiles cleanly too in VO? If it does, I am curious.

Something floating on top of my head....

Thanks,

Rene

Hi Rene,

of course!
Currently I'm working on the VO version of this application, and before I start working again on the migration, I will xPort the application again.
All changes are made on the VO side (or together on both sides), so the application versions remain in sync.
Things that can compile in VO are corrected there, and things than cannot compile in VO are put in the VO code surrounded with #ifdef statements like the code I posted in my last message.

This migration strategy was not invented by me, but the credit goes to Dieter Crispien and Meinhard Schnoor.

Wolfgang

I hear and I understand ;-0) And sort of agree as well !?

However, I am a confirmed .NET coder these days, and love X# syntax etc., a lot. So I wish to use as much of the modern .NET and Roslyn components as possible.

Remember I gave up on using Vulcan for two years after I found the beauty and benefits of using .NET 'LINQ' with Entity Framework (EF) - yes, its that good. This meant I could give up using ADO directly (which I had done for over 2 years), and move to ORM with EF6. All my SQL work is done in X# - on the object side of the ORM 'interface'. This saves me MUCH development time, and gives me better designed databases and tables, and more. And LINQ works "hand in hand" with EF6. The amount of code is less as well.

Now then, you can use Postgres with EF6, I would guess the correct 'driver' exists, so that is also one other option. I will check on this for the Forum.

By the way, I thought this thread started about looking for possible light weight SQL possibilities, and thought also that the Forum was about .NET and X#, as opposed to Unix. (Head scratch.)

I use the VS integration of the SQL facilities more to check what my X# code has done for me with EF6 than for any original design.

So if I had to choose, using your "checks and balances" of MS stuff used, I would give up Office and use SQL Server with EF and LINQ. Oh! and will keep using Visual Studio as well.

You all may be interested to learn of a test I did this afternoon. I downloaded and installed a new and fresh version of the 'LocalDB' part of SQL Express 2017 - less than 200 Mbytes. Then used it to create a new database (simple with one table 5 columns, and a few lines of data). I detached the database, and then I went over to full 'SQL Server instance' and attached the 'mdf'. And as I had thought/hoped it would, the data file was compatible with the full server instance. This to me is a real benefit to the 'Local DB' possibility. Transferable data (back and forth) - as it should be in a sensible world.

On the other side of my feelings for Microsoft, I am pretty pissed-off that METRO apps got the heave-oh, and that Windows phone never really got off the ground ;-0((

I could survive with 'Google Docs', - BUT - , can't do without the .NET stuff above.

By the way guys, LINQ is over ten years (yes 10) old, it first was available in VS 2008.

Isn't it amazing just how old this 'new stuff' can be ;-0)

Have a nice weekend,
Regards,
Phil.

Hi Phil,

fortunately we can have different opinions... Agree sometimes and disagree sometimes.

And fortunately we have partially different opinions, because a discussion can start only because of different opinions. And sometimes we can change our mind, and sometime we don't...

Wolfgang