You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See the following two community forum threads: here and here.
Expected behavior
Credentials should be saved successfully and the binding process completed.
Actual behavior
The binding process failed.
Known workarounds
None
Related information
SonarLint for VS Version: 4.6.
Visual Studio Version: ?
Languages in your solution; C#
Notes
We've been unable to repro the issue locally.
The Failed to write credentials error message is thrown by the Microsoft.Alm.Authentication component as the result of a failed Win32 API call. The API is throwing Win32Exception which should have the HRESULT error code. Unfortunately, we aren't logging that part so we're losing the Windows error code.
In the absence of a repro, we could amend the logging to capture the Windows error code to give us a better idea of what the underlying issue might be.
The text was updated successfully, but these errors were encountered:
I get one additional line before the "Failed to write credentials" error.
"Ruleset binding: all projects need to be updated reference the generated ruleset."
Every time the binding tries to run, an additional ruleset file is added to every project.
Saving everything. Closing VS, and reopening appears to have corrected it.
I got a message that the profile was "out of date", and after clicking "Update" I seem to be connected.
Description
See the following two community forum threads: here and here.
Expected behavior
Credentials should be saved successfully and the binding process completed.
Actual behavior
The binding process failed.
Known workarounds
None
Related information
Notes
We've been unable to repro the issue locally.
The
Failed to write credentials
error message is thrown by theMicrosoft.Alm.Authentication
component as the result of a failed Win32 API call. The API is throwingWin32Exception
which should have the HRESULT error code. Unfortunately, we aren't logging that part so we're losing the Windows error code.In the absence of a repro, we could amend the logging to capture the Windows error code to give us a better idea of what the underlying issue might be.
The text was updated successfully, but these errors were encountered: