Unable to update to SpecFlow 3. Project wont compile PathTooLong Error

[ylerner43]

Issue Upgrading to SpecFlow 3.0 from 2.4.1. The following exception is thrown when trying to compile:

Exception is thrown this could be caused by extension.

From Logs:
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(String path) 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, HashSet1 variableColumns) at Microsoft.VisualStudio.Shell.TableControl.Implementation.TableControl.UpdateEntries(HashSet1 variableColumns, Boolean anyColumnChanges, List`1& frozenSinksAwaitingDisposal) at Microsoft.VisualStudio.Shell.TableControl.Implementation.TableControl.d__165.MoveNext() --- End of stack trace from previous location where exception was thrown --- at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

I dont have any paths that are that long, I have ran the program to find out.

My set up is Win 10 (Brand New machine) VS 2017, latest update. MS Test (2.0), .Net framework .4.7.1

As soon as I go back to SpecFlow 2.4.1, problem disappears

[kaelanhr]

I consistently have this issue and often it causes issues with my visual studio error list and compilation. I can usually fix it by removing all my code behind files and rebuilding again.

[SabotageAndi]

You have this issue when you compile the project?

[kaelanhr]

You have this issue when you compile the project?

In my case it does it when visual studio loads. Its not the fact that it will not compile it is that it will not populate the error list. My theory is that it has to do with the number of feature files in my project, in my case i have several hundred tests.