I have run into issues with VisualStudio - both 2017 Pro and 2019 Pro. If I try to open my solution, I get this error:
The error message in VS2019 is a bit different but with the same meaning. As I investigated the ActivityLog file, there is only this node interesting regarding this issue:
<entry>
<record>698</record>
<time>2019/07/03 08:14:00.064</time>
<type>Error</type>
<source>Editor or Editor Extension</source>
<description>System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)

at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)

at System.IO.Path.InternalGetDirectoryName(String path)

at Microsoft.VisualStudio.ErrorListPkg.PathColumnDefinition.GetCachedDirectoryName(ITableEntryHandle entry)

at Microsoft.VisualStudio.ErrorListPkg.PathColumnDefinition.TryCreateStringContent(ITableEntryHandle entry, Boolean truncatedText, Boolean singleColumnView, String& content)

at Microsoft.VisualStudio.Shell.TableControl.TableEntryHandleExtensions.TryCreateStringContent(ITableEntryHandle entry, ITableColumnDefinition column, Boolean truncatedText, Boolean singleColumnView, String& content)

at Microsoft.VisualStudio.Shell.TableControl.Implementation.TableControl.GenerateFiltersForColumn(UpdateResults results, ITableColumnDefinition columnDefinition)

at Microsoft.VisualStudio.Shell.TableControl.Implementation.TableControl.UpdateEntryFilters(UpdateResults results, HashSet`1 variableColumns)

at Microsoft.VisualStudio.Shell.TableControl.Implementation.TableControl.UpdateEntries(HashSet`1 variableColumns, Boolean anyColumnChanges, List`1& frozenSinksAwaitingDisposal)

at Microsoft.VisualStudio.Shell.TableControl.Implementation.TableControl.<UpdateEntriesAsync>d__182.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)</description>
</entry>
Is there any way how to figure out exactly what path is wrong? I suspected that SpecFlow addid had been causing this issue. But if I disable this addon, nothing changes.
Another teammate does not have this issue with the same solution.
I somehow got rid of this error message. I don't understand how, but let me share steps I did.
Once I found the bad one, I reverted all the changes on GIT.
I repeated this approach for files and folders within this project. As I deleted some files and restarted the VS, the problem disappeared.
Again reverted all changes on GIT.
Voila, the error is history in both 2017 and 2019. Nothing changed in SLN or CSPROJ files.