Skip to content
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

Open
audiamus opened this issue Jun 7, 2022 · 2 comments

Comments

@audiamus
Copy link

audiamus commented Jun 7, 2022

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:

---------------------------
Microsoft Visual Studio
---------------------------
The source control provider associated with this solution could not be found. 
The projects will be treated as not under source control.

Do you want to permanently remove the source control bindings from the projects?
---------------------------
Yes   No   Help   
---------------------------

Clicking "No" seems to bypass the problem and AnkhSVN appears to work.

@GaryWayneSmith
Copy link

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.

@arteny
Copy link

arteny commented May 30, 2024

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.
Also I found that here " Tools > Options > Source Control" setting looks like was changed to "Git" with some of last product update.
So changing back to TFS fixed the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants