What happened to Oxygene Elements 10?
What happened to Oxygene Elements 10?
I'm maintaining a Delphi XE very large project that runs in both compilers (Delphi XE and VS 2015 with OE 9). There's a need to move to VS 2017 but in order to migrate we need OE 10.
With VS 2017 and Oxygene 10, over 37.000 lines errors are raised when compiling the project that works perfectly under Delphi (VCL) and VS (2015 OE 9) sharing the same code base using #IFDEFs
Googling a little a found out that Oxygene decided to change the way #IFDEF works under OE 10. They think it's "ugly". Well... over 37.000 lines of errors are not pretty either. Especially if you will loose compatibility with Delphi/FP in the "fixing" process.
How are you managing? Is there any word ( or works ) from Oxygene that will solve that bug.
Is there an OE 9 that works with VS 2017?
Clément
I'm maintaining a Delphi XE very large project that runs in both compilers (Delphi XE and VS 2015 with OE 9). There's a need to move to VS 2017 but in order to migrate we need OE 10.
With VS 2017 and Oxygene 10, over 37.000 lines errors are raised when compiling the project that works perfectly under Delphi (VCL) and VS (2015 OE 9) sharing the same code base using #IFDEFs
Googling a little a found out that Oxygene decided to change the way #IFDEF works under OE 10. They think it's "ugly". Well... over 37.000 lines of errors are not pretty either. Especially if you will loose compatibility with Delphi/FP in the "fixing" process.
How are you managing? Is there any word ( or works ) from Oxygene that will solve that bug.
Is there an OE 9 that works with VS 2017?
Clément
Carlo Kok You can track our message in your support forum. Here is the link : https://talk.remobjects.com/t/compilation-error-v-10-0-0-2305-with-vs2017/16970
ReplyDeleteWe reported 6 days ago.
Hope you can help.
David Heffernan Yes there are. I'm already studying a Delphi to C# transpiler. Depending on RemObject answer we will completely bypass Oxygene.
ReplyDeleteReplied Clement Doss to your post.
ReplyDelete