SingleFileISense

[Beth]

I have been searching for information, but haven't come up with anything yet.

If you can send and email to support, then we could try taking a closer look in a meeting and see if i can see anything that way.

[Mordachai]

I'm also working with VisualAssist on this - as I think it may be due to VA opening wrong files - which is somehow causing VS2015 to think "hey - let's [stupidly] add that automatically to your project!!!"

Update: Thursday morning - I've disabled single file I-sense. So hopefully this won't recur even if VA or something accidentally opens the wrong file again. We'll see.

It does beg the question: maybe Vault needs to filter out such files?

[Beth]

Just an update for future readers. If you run into the same issue, please send an email to support with details. I do not have a resolution yet, though it appears that turning off Visual Assist may have helped. I will update this thread again if I find out more.

HS: 247125

[kl-baerchen]

Hello Beth,

i believe it is the same problem we have and, sorry, which still exists.
Our thread: http://support.sourcegear.com/viewtopic ... 980#p77980

Best regards
Markus

[Beth]

kl-baerchen: let's continue in your thread rather than mixing these two up. If we find a resolution, I'll post back to this one.

[Beth]

As an update, we may have pinpointed the change in VS 2015 that causes this. It's logged with the developers and is expected to be fixed with Vault 10.

The work-around is to turn off single file intellisense.

F: 19683