4.50 perfectly works in vs2019 as well (at least for now), if you don't have custom plugins that are built in vs2022. Just turn off warnings about unsupported target framework in vs2019 and rebuild the solution. But this is at your own risk, the recommended way to use vs2022.
4.50 perfectly works in vs2019 as well (at least for now), if you don't have custom plugins that are built in vs2022. Just turn off warnings about unsupported target framework in vs2019 and rebuild the solution. But this is at your own risk, the recommended way to use vs2022.
Ah ok, thanks for that Romanov! I did try to build the 4.50 beta in 2019, but of course, hit issues. I'll look at suppressing the warnings, and see how I get on.
I am running windows 10 and VS2022 not having any crashing issues porting our site from 4.3 to 4.50.1. Maybe I should not jump to a conclusion to soon as I see there is an update this morning I have not applied. Will see what happens?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.