VS designer assemblies incorrectly handles modern .NET SDK searching

Hi! I’ve found that both 2019 and 2022 designer packages incorrectly handles modern .NET SDK searching in case if OS culture is using comma (“,”) as decimal separator (instead of dot “.”). I’ve spent almost a day trying to determine where is the problem with my OS or .NET 6.0 SDK installation because WiseJ wizard was not seeing my .NET 6.0 framework. Finally I’ve decided to look into wizard code with dnSpy to see how it determines and enumerates SDK installation and found that it is trying to convert f.e. “6.0” to float number and fails, because my locale culture uses “,” as separator. I’be slightly modified your code with dnSpy to test it and now it works correctly (and should work now for any culture with any separator). Please look screenshots of original and modified code.