No announcement yet.

Afterwarp for .NET ?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Afterwarp for .NET ?

    Are there any plans to support c#/.net? It will be better if there is more choices.
    Think about some of people that will be attracted to this engine.

  • #2
    Yes, C# bindings are amongst highest priorities so they will be coming soon.


    • #3
      Can't wait to see. hope it won't take too long.


      • #4
        Well, first Afterwarp v2 is coming shortly and it comes with C/C++, Delphi (including support for Delphi Sydney 10.4) and FreePascal/Lazarus. C# bindings will come out next - we already have some partial work done on this previously, but it was for Afterwarp v1, so it would be the question of updating the bindings.


        • #5
          How about the progress, C# bindings plan has been stopped ?


          • #6
            There have been some delays due to quarantine and closures, but C# bindings are coming soon along with Android support.


            • #7
              As an update, we are still preparing Android support, which has been available in experimental form to some of our customers. It will come publicly within next few months. Also, for the past months, significant work has been performed on new framework features which did not get into latest v2.0.1 update and are yet to be announced.

              However, so far we didn't have opportunity to progress on .NET bindings as we don't have enough workforce to accommodate for it. The main challenge for us is to create an automated tool for generation of headers from existing C declarations. For Delphi and FreePascal/Lazarus headers, we are using HeaderParser tool, so we would need a similar tool to generate headers for C#. If there would be someone who would be wiling (on paid basis, of course) to develop such tool from scratch, or modify HeaderParser to build C# headers instead, please contact us or send me a private message on the forums.

              As such, the framework comes with very simple C interface so it would be relatively easy to manually create .NET headers for it. However, when the public API changes as we incorporate new features and improvements, we need an automated tool to do it instead of spending time each time fixing the headers. In the past, it has proven to be very time-consuming to be updating Pascal headers manually each time, which is why we switched to use HeaderParser tool.