Anyone have a workaround for the Visual Studio 2017 long path issue

[aceroraptor]

Hi,

I have updated  my SpecFlow Automation to Visual Studio 2017, SpecFlow VS 2017 extension, SpecFlow Package V3.0.220, 

I get frequently upon Visual Studio startup the below error at the Visual Studio Activity Log

<entry><record>736</record><time>2019/06/26 14:55:09.344</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(String path)

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

   at Microsoft.VisualStudio.Shell.TableControl.TableEntryHandleExtensions.TryCreateStringContent(ITableEntryHandle entry, ITableColumnDefinition column, Boolean truncatedText, Boolean singleColumnView, String&amp; 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&amp; frozenSinksAwaitingDisposal)

   at Microsoft.VisualStudio.Shell.TableControl.Implementation.TableControl.&lt;UpdateEntriesAsync&gt;d__165.MoveNext()

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

   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)</description></entry>

At the Build output view I see the following text (attached) which seems to be the cause of the long path issue.

This results in a bit of an erractic compiling operation for SpecFlow, when I add a couple of new test cases I have to restart VS 2017 so my test cases appear in Test Explorer.

Has anyone else encountered this?

Best Regards 

[Ranjeet Jain]

Hey - Change the long path to poitn to C drive and that solved our issue.

[aceroraptor]

I am encountering this issue as well, it is a issue with Visual Studio 2017 that I am hoping is resolved in 2019.  Waiting on work to have an approved package for Visula Studio 2019.

I has an established SpecFlow project that I upgraded to SpecFlow 3.0.  I feel totally your pain as this is beyond frustrating.

On Wednesday, June 26, 2019 at 11:09:59 AM UTC-4, aceroraptor wrote:

[Gáspár Nagy]

Both the "SpecFlow for Visual Studio" and the "Deveroom for SpecFlow" packages work with VS2019 and SpecFlow v3. 

Or do you have to let them approved by your company?

--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/specflow/2f6b1b64-7437-4aa5-a801-e6416dafeb70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andreas Willich]

If you have problems/issues, please open an issue on GitHub:  https://github.com/techtalk/SpecFlow

About your issue: in the Stacktrace is no where anything to read about SpecFlow. Why do you think it is SpecFlow?

To view this discussion on the web visit https://groups.google.com/d/msgid/specflow/CA%2B%3D5S%2BTaY3542Z%2BnK3Wnjfq1NkMKWF%2BQKoPYnb%3DEG6vx9FCDOA%40mail.gmail.com.