how to read racket source in visual studio?

[SpicesEx]

I executed the build.bat command in C:\Users\xxxxxx\Desktop\racket\racket\src\worksp according to the instructions of the readme.txt, and everything ran normally, and racket.exe and other things were successfully generated. When I want to read the source code, I found three *.sln files in C:\Users\mingy\Desktop\racket\racket\src\worksp\racket\, which are racketX.sln;

racket9.sln; racket.sln, I opened racket.sln and saw that each project name in visual studio has the (2010) suffix added. When I opened racket9.sln, I encountered a reminder to upgrade some things (I'm sorry I I forgot to take the screenshot during operation), when I tried to open racketX.sln, it just opened normally without any reminder.

I want to ask what are these three *.sln?

If I want to read the source code of racket, which of the three should I open?

Operating system version: windows10 1909; 18363.1019

visual studio 2019.

By the way, I would like to ask whether this kind of question should be sent to the dev channel or the user channel. I am very sorry if it disturbs you.

[SpicesEx]

I‘m sorry,I has find the answer in readme.txt ,I should read more carefully before asking question, please delete this question..

```

Traditional Racket implementation's CGC variant can be built and

debugged using visual Studio solutions and project. (See

"..\racket\README.txt" for information on traditional Racket

variants.) Further steps using the command line can then build the 3m

variant and related executables.

The CGC implementation is split into several projects that are grouped

into a few solutions. To build the `X' solution with Visual Studio,

open the file racket\src\worksp\X\X.sln, but add `9' before ".sln" if

you're using Visual Studio 2008 (i.e., version 9.0). The solution

files without a number are for Visual Studio 2010, but they should

upgrade automatically for later versions.

 [The .vcproj files are used by the ...9.sln solutions, while the

  .vcxproj files are used by the other .sln solutions. The latter are

  compatible with Visual Studio 2010. For Visual Studio versions later

  than 2010, "build.bat" script auto-upgrades projects in a copy whose

  file name ends with a literal "X" to match the current tool version,

  but you can also just upgrade them within your version of Visual

  Studio.]

```