Quote:
Is it the development part it self?
Is it the testing part after having developed the architecture support before being able to release it to public?
Is it the support after having it released?
All of the above.
It's impossible to estimate the effort required for something like this, because ultimately it involves fixing everything until it works. We simply don't know how many hangups will exist, and it could be months into the work before realising that it was a terrible idea to try.
We are integrated at so many levels of the platform that regardless of how well the platform handles adaptation to ARM, we will have stuff that slips between the cracks.
It also means that assuming we do implement it, the entirety of the product needs to maintained on it.
Unfortunately there is simply no where near enough demand for this to justify the time and effort required. Basically, I'd be setting myself up for a potentially tragic loss that could even sink the product entirely. It would be rather irresponsible, actually.
Quote:
Also I just saw you're still supporting VS down to version 2010 (do people still even use it??). Could cutting support for older versions be a solution to free ressources maybe?
Removing support for the older versions of VS will actually cost more time that it will save at this point. We would need to migrate a lot of tests and environments to do this. With VS2008, it was worth it because there was no WPF UI for it, so we couldn't upgrade parts of the UI without considering it. VS2010 has the same basic UI as VS2022, though some areas of the integration and core platform are clearly very different.
Quote:
Edit: btw: is it possible to change my account name in this forum?
Unfortunately not, but it IS possible to set up a new account and transfer all details over to it (such as email, licenses, etc).
