RonaldK

What benefits do you expect from this? Performance: I doubt that an ARM IDE will really be faster than the current x86 version?

Yes. I'm using it with Chrome remote desktop. (https://remotedesktop.google.com/access/) You can't operate the login screen with it, but everything else can.

All these points: Is this "roadmap" interesting for new or existing customers? Hard to believe that many existing customers stay in maintenance after reading this. So there was a good reason why no more roadmap came out. There is nothing in the pipeline. I hope Embarcadero's missing roadmap isn't for the same reason.

It's probably more about the Embarcadero development team. Isn't the Idera development model made up of freelance developers? Aren't they mostly based in Ukraine and Russia? Perhaps this development model currently has serious problems.

This "playing dead" is now finding more friends. DevExpress no longer publishes a Delphi roadmap for 2022 either. Is this a good sign too? https://supportcenter.devexpress.com/ticket/details/t1072425/vcl-roadmap-2022

https://blogs.embarcadero.com/de/rad-studio-roadmap-november-2020/ This ends with Delphi 10.5. The silence can be understood in one way or another.

What new functions are planned for Delphi anyway? Is there still a roadmap for Delphi? I haven't found any more. For example, what about continued support for the iOS Simulator? That was on the old roadmaps for a long time, but has it all been lost now? What about the better code generation of the "nextgen" compilers? Delphi has some other work to do at the base. More compilers/platforms are not helpful here.

I don't think he will help me. I know the answer: Windows 2019 is not supported Unfortunately I didn't have a good experience with the Embarcadero support.

All .NET updates are installed but the problem persists with the new .NET version (4.7 -> 4.8) Name der fehlerhaften Anwendung: bds.exe, Version: 28.0.44500.8973, Zeitstempel: 0x6227d05c Name des fehlerhaften Moduls: clr.dll, Version: 4.8.4470.0, Zeitstempel: 0x61b731cd Ausnahmecode: 0xc00000fd Fehleroffset: 0x004d556a ID des fehlerhaften Prozesses: 0x1140 Startzeit der fehlerhaften Anwendung: 0x01d848c22be05e31 Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Embarcadero\Studio\22.0\bin\bds.exe Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

It doesn't help. The Refactoring menu is gone, but the IDE still dies anyway. Some .NET libs are still loaded by the IDE: Borland.Build.Tasks.Common.dll Borland.Studio.Vcl.Design.Refactoring.dll and many more.

Yes. The Event Log log the first occurrence at 18.Feb. 2022. Delphi 11 previously ran without this problem. Maybe a .NET update brought this problem.

I'm working on Windows Server for many years. So far there have been no problems. This new .NET issue has been popping up for the past few weeks. I think it has more to do with .NET than with Delphi. Maybe Remy's suggestion will help.

I'm not using refactoring. Is there a way to disable/remove the refactoring from Delphi?

Same situation with the latest Delphi 11.1 Name der fehlerhaften Anwendung: bds.exe, Version: 28.0.44500.8973, Zeitstempel: 0x6227d05c Name des fehlerhaften Moduls: clr.dll, Version: 4.7.3910.0, Zeitstempel: 0x61b3f594 Ausnahmecode: 0xc00000fd Fehleroffset: 0x004559ad ID des fehlerhaften Prozesses: 0x57c Startzeit der fehlerhaften Anwendung: 0x01d83e9a646f0d6d Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Embarcadero\Studio\22.0\bin\bds.exe Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll For what functionality does Delphi use the .NET framework? Anything that I can switch off?

Delphi need and use it. If you look to the Delphi .NET libs. They need 4.x: // C:\Program Files (x86)\Embarcadero\Studio\22.0\bin\Borland.Build.Tasks.Common.dll // Borland.Build.Tasks.Common, Version=28.0.0.0, Culture=neutral, PublicKeyToken=91d62ebb5b0d1b1b // Global type: <Module> // Architecture: AnyCPU (64-bit preferred) // Runtime: v4.0.30319 // This assembly is signed with a strong name key. // Hash algorithm: SHA1 Since this crash also happens when not working in the IDE, I suspect it might have something to do with .NET's garbage collector.