AnkhSVN icon indicating copy to clipboard operation
AnkhSVN copied to clipboard

Source Control error during solutions opening

Open Yawn0 opened this issue 3 years ago • 6 comments

In our working group we are using AnkhSVN to manage projects. Since march/april every time we open up a solution this message box that says : "the source control provider associated with this solution could not be found. The project will be treated as not under source control. do you want to permanently remove the source control bindings from the projects?" opens.

We cant figure out how to fix this problem. We are using Visual studio Enterprise 2017 an the latest version of AnkhSVN. Screenshot 2021-08-03 120418 Screenshot 2021-08-03 120335

Yawn0 avatar Aug 03 '21 10:08 Yawn0

Did you get an initial load error an AnkhSVN on an earlier start of Visual Studio?

Looks like the main package is somehow disabled.

rhuijben avatar Sep 16 '21 07:09 rhuijben

We fixed the issue by manually specifing the provider in the csproj file

<PropertyGroup>
    <SccProjectName>Svn</SccProjectName>
    <SccLocalPath>Svn</SccLocalPath>
    <SccAuxPath>Svn</SccAuxPath>
    <SccProvider>SubversionScc</SccProvider>
</PropertyGroup>

We couldn't find a solution for projects that aren't in the new SDK style.

I believe it is related with async plugins load where simply the ankh plugin gets loaded after the message box. It doesn't always happen, so I tend to believe some sort of race condition.

Rand-Random avatar Nov 02 '21 13:11 Rand-Random

Hmm, interesting.. Haven't seen this issue myself yet, but my current employer works with git so I don't see these cases that often any more. Patch or reproduction recipe for somebody with AnkhSVN debugging setup would be very useful.

rhuijben avatar Dec 09 '21 13:12 rhuijben

This could be relatated to issue #44, which just got a workaround.

rhuijben avatar May 02 '22 10:05 rhuijben

The only solution we could find was to pass to a previous stable version of Ankh SVN

Yawn0 avatar May 03 '22 13:05 Yawn0

Would it be possible that you or a colleague tests the last build from GitHub Actions, to see if it fixes this issue for you?

rhuijben avatar May 03 '22 21:05 rhuijben