I have a working VS2022 Enterprise (NOT VSCODE) Solution on Windows 11-Pro. I wanted to add Source Control to it. MANY years ago, I had created a github account (DocDJ) which still holds an old repo. Using Github, I created a new private repo (M_exifier_threaded). I turned on Source Control (using git commands, becuse doing iy with VS fails) and after 3 days of attempts, got my existing solution folder initialized and pushed to my git repo. Along the way, I must have done “something”, that created a clone in an old local directory (“E:GIT-personal-reposDocDJ”).

At this point, I can’t open the original VS folder’s .sln (all the old code and .git and .vs are still there), but I CAN open the Solution from “E:GIT-personal-reposDocDJM_exifier_threaded”.

I was hoping to keep everything in the original folder if that is possible, so I could turn off Source Control and have only my latest version of the code in it. However, I do see the advantages of keeping my repo in a separate folder.

I have not made any changes to the code, so I am quite willing to start from scratch, if I can get that original solution working.

So my question is: can I fix my old VS folder so the code is usable (as-is) without GIT turned on (if I decide to stop using Source Control) and still use the code from the repo in the…DocDJ folder OR can I make the original folder usable with git and drop the folder in E:?

I tried to open the existing VS folder and got an error message that the .sln file is not a valid Solution file.

VS IS able to open the .sln in the cloned version, but when I do a build (no changes made), I get 100’s of syntax errors and an error that it attempted to compile an old file that was excluded from the old build process and did not even exist in either of the folders. The clone is also missing the Solution properties and configuration files, so I can’t tell VS what compiler version to use. So the clone is not complete.