Ask and you shall receive, an answer anyway.
I started with a clean system, because I was silly enough to try installing VS2017 on my previous build.
(I say silly because I run a Win7 system modded to look/mostly work like 2K/XP, and VS2017 happily borks that setup.)
Install VS2013, with MFC, I used pro since I was able to borrow then later purchase a copy second hand.
Your mileage with express or community may vary, I don't run either of them because I will not have any M$ accounts.
Install MBCS (Multibyte character support), this is because M$ dropped everything non unicode for VS2013, then brought it back in VS2015 when they figured out they couldn't force everyone to drop multiplatform programming.
You can get it from M$, or from my downloads if you like.
I also have prebuilt celestia versions as well.
Be sure editor has line numbers turned on, you WILL!!! get lost without them.
(Tools/Options/Text Editor/'C/C++'/General/Settings/Line numbers)
Grab the source from github(Current version I just grabbed is VS2013-x86-x64 and has 5270 commits)
I made a clprojects directory, put the source zip into it.
Extract zip in place, this creates a vs2013-x86-x64 directory.
Start VS2013, open /clprojects/celestia-x86-x64/celestia.sln and be patient.
It has to build a file index the first time you open it, and it can take a while.
From Build, select Batch Build, check x86 & x64 release, and compile.
Be patient once again, it takes a while.
This will, assuming the moon is in the right phase, jupiter hasn't wandered off, and Venus is in a good mood.
Give you Celestia-x86.exe & Celestia-x64.exe in /clprojects/celestia-x86-x64 where you can find them easily.
The only requirement you should have at this point, is that the VS2013 redists need to be installed.
Both versions, x86 & x64, are fully statically linked, requiring no support dlls to run.
I have built VS projects for each of the support libraries, and compiled them with VS2013.
They are intended to go in /clprojects beside celestia, then have headers and libs copied as needed.
This is so that when the time comes, VS2015 can be embraced by recompiling as needed.
I am still working out some bugs, but they are compiling, linking, and displaying properly.
Once I am done, I will sending them Alexell so he can put them up on their own.
If you are wanting to compile with QT, then all you need to do is install QT creator.
The code compiles with QT 5.4/5.6/5.8/5.9 in 32 & 64 both.
Though QT does require a matching libintl.dll & QT support DLLs both.
The QT DLLs include those in a pair of subdirectories in addition to the ones in the Celestia root.
An example is in my downloads, which is VS2013 w/QT5.4, and should run on any windows system with VS2013 x86 redists installed.
I should have an x64 version up this weekend if my life stays on track.
I hope this answers any questions anyone has.
Also, I am working on making a Mingw compiled version of Celestia using Mingw5.30 available with QT, and I am nearly done preparing the support libs.
Once I have done that, I will move on to 64 bit, which I have located elsewhere, but is the same version QT has.
Then VS can be abandoned if need be, since I can concieve of no circumstances under which I will ever install VS2017.
I will only be testing with VS2015 once I can afford a copy, and it is not cheap.
I say again, no express or community version for me since I will not have an M$ account, ever.
I repeat myself on that only because I keep getting reminded it is free.
I have reasons, and they are permanent.
I hope this is able to help people get in motion.
The more people are working on it, the more can be done.
P.S. I have also put up a solar system tour on DVD made using Celestia, if anyone is willing, I would like to get some feedback.