In #19, SA1649 was updated to not trigger on Razor pages as they are created by Visual Studio. This is the important step, but could possibly be improved further. If a Razor page model file is not named according to the expected convention, a code fix is provided which would change the file name without taking the Razor page convention into account. Might be worth looking into the complete behavior and to improve the analyzer and/or the code fix.
In #19, SA1649 was updated to not trigger on Razor pages as they are created by Visual Studio. This is the important step, but could possibly be improved further. If a Razor page model file is not named according to the expected convention, a code fix is provided which would change the file name without taking the Razor page convention into account. Might be worth looking into the complete behavior and to improve the analyzer and/or the code fix.