![]() As such, the developer experience (even without the use of third-party components) leaves much to be desired (small UI elements, unreadable text, etc). Visual Studio 2012/2013 do not support High DPI screens (common across most enterprises today).It is time consuming and at times extremely problematic to deliver a high quality design time experience for old IDE versions. NET Framework components (project templates, component designers and wizards) operate flawlessly in these old IDEs when (and only when) newer IDE versions are installed on the same machine side by side (for instance, Visual Studio 2015, 2017, 2019, 2022 – as these IDEs install the necessary .14.0 - or newer - assembly). The reasons we have chosen to drop support for these older IDEs include: Visual Studio 2012/2013 - Deprecation in Our v22.2 Release CycleĪt present (v22.1), design-time for our. NET Core-based development will be affected. ![]() NET Framework customers in any manner - only. NET 6 and Visual Studio 2022 (v22.1 and higher). These changes do NOT affect. Worth noting that our ASP.NET Core Blazor-based products ( Blazor Components, XAF UI, Web API Service) already require. In our v22.2 release cycle, DevExpress .NET Core-based WinForms and WPF products will – at a minimum - require .NET 6 and Visual Studio 2022. NET Core support for Visual Studio 2019 for our desktop products (since this IDE version does not support. First, a quick reminder: This year we intend to deprecate. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |