Bug with long pathnames about git-tools

[denisz1]

Quite ironically, the reason I started using this extension rather than the built-in VS git provider, is that the built-in one continually scans that directory as well!

So both providers have the same bug! :-)

[yysun]

I will try to re-produce and fix it. If you can send the error log, it will
help me to find out where it goes wrong.

On Fri, Dec 5, 2014 at 11:46 PM, denisz1 [email protected] wrote:

Quite ironically, the reason I started using this extension rather than
the built-in VS git provider, is that the built-in one continually scans
that directory as well!

So both providers have the same bug!

—
Reply to this email directly or view it on GitHub
#1 (comment).

[yysun]

@denisz1 I was able to reproduce the issue and see the stack trace. It looks like a visual studio API bug. I used the API to detect file changes under solution folder. I guess Microsoft GIt Provider uses the same API, so it crashes too. I have raised a question to MSDN forum. https://social.msdn.microsoft.com/Forums/vstudio/en-US/9898f6d9-a448-4fdb-b693-ec9bfd8c4c42/ivsfilechangeeventsfileschanged-crashes-with-systemiopathtoolongexception?forum=vsx

We will see if they can provide a workaround. Meanwhile I will try a different method without using the API.

[denisz1]

@yysun Thanks for the update!

Yes there seems to be a problem with VS. There was a bug report on Connect, so I guess the VS team knows about it.

Is it not possible to manually ignore the node_modules directory, until they release a proper fix? Because that could be a while, maybe until VS2015 is released.

I hope there is another way to solve this problem! This extension is great...

[yysun]

The issue has been fixed in 1.3.1. Uploaded to Visual Studio Extension Gallery.

[denisz1]

@yysun It works! Thanks Yiyi!