-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual Studio 2022: "Source control provider associated with this solution could not be found" #53
Comments
I have been running 2.9.87 for some time under VS 2022 without issue. Then about 3 weeks ago I created a new project that contained about 3,000 files. This was originally a VS 2019 project that I upgraded to 2022. After that, the solution started raising the same warnings. So, just for the fun of it, I created a brand new project with the same name (which allowed me to run it as a standard 2.0 instead of .Net Framework 4.6.2) and copied over all of the class files manually, imported them into the project using include, and the same thing happened. I was hoping that it was just the 2019=>2022 migration but that does not seem to be the case. It really didn't like the 3000 files. For the other projects that I also upgrade from 2019 to 2022, it works fine. |
Reproduced for me for latest VS build now. Nothing was ported between VS. Just saddenly it begins reproduced on open solution. Pressing No in dialog connects to TFS(git) well. |
Same thing for me. From 17.9.6 to 17.10.3 and after each time I open my solution, got this message. I say "NO" and still connected to DevOps and can work. |
The first time a solution under github is opened in VS2022 appears to be working however does not have latest code. All subsequential times I open the solution VS2022 prompts this message about Source control provider associated with this solution could not be found. Help doesn't work and don't really know how to resolve it. I even tried to remove the project and bash it again from github, it works the first time i open it again. This is on Wondows 11 by the way |
Visual Studio 2022 Community Edition, 17.2.3
AnkhSVN build from source, June 3.
Starting up any solution in VS2022 with AnkhSVN source control pops up this message box:
Clicking "No" seems to bypass the problem and AnkhSVN appears to work.
The text was updated successfully, but these errors were encountered: