reflaxe.CSharp as a replacement for Haxe dropping C# support?

[mesheets]

As I've learned that C# will be dropped from the next major version of Haxe, I wondered if reflaxe support for C# is still being actively pursued here, or if a C# or .NET target will no longer be available within the Haxe ecosystem.

Thank you!

[jeremyfa]

Reflaxe C# is still a plan, at least as far as I’m concerned, although there is no ETA at the moment and I’m quite busy on other subjects right now.

Meanwhile, current c# target works fairly well and will not disappear anytime soon as long as Haxe 4 can be used

[mesheets]

Thanks, I had been considering Haxe for a new open source project that will in part entail .NET but don't want to end up in a dead-end situation where the C#/.NET target for Haxe is deprecated with no easy path forward.

Also, HaxeFoundation/haxe#5480 to support .NET Core (now called just ".NET") was closed as "not planned," so that has been another hesitation. From the reflaxe.CSharp test code, though, it appears there is an intent here to support SDK-style project files that have targets such as .NET (Core) and/or .NET Standard?

[neimanpinchas]

Just adding here as its matching the title.

Haxe stopping support for c# would mean we are losing intellisense for dotnet dlls, which was a huge timesaver that enabled using dotnet classes directly (leaving no reason to use c# directly)

To replace that we will need a command line tool that could generate a tree of extern files for some DLL, It would be fun to port the OCAML PE reader code to haxe to support such a tool

[neimanpinchas]

Sorry I see #1