CODEWITHSUNDEEP
tfsvisual-studio-2015azure-devops
Ian
Ian

Reputation: 4919

TFS in VS2015 works for .csproj, not for adding .cs

Three computers all running Visual Studio 2015 with all current updates. All three machines have Bitlocker running.

Same problem occurs on all three machines, all three were working fine perhaps a week ago (last time I used this solution).

I use VisualStudio.com for TFS.

Today I got latest, added a file to a project I was working on, edited it and went to check in. I noticed it wasn't in the pending list. HOWEVER, the .sln was checked out and the .csproj was updated. I could manually add the .cs file to TFS and it happily checked it in. It just won't do it automatically.

I then created a new project and added it to TFS and this worked fine.

I opened another existing solution and that also works fine.

So I duplicated the whole solution directory and attempted to add it with TFS power tools and NOW I see the problem.

Excluded by the global exclusion list: *.lib

My guess, and it's only a guess, is that in the last update, pushed out in the last couple of weeks they've added some exclusion for something "webby" which is screwing up my solution that happens to have a project with .lib at the end. Or perhaps file level filters are now applying to directories?

1) Where are these exclusions set?

2) Anyone know if this is a new exclusion added recently? As I said, I've worked on this solution for a year or more on and off without problem until today.

3) Which language prefers *.lib to be excluded? It makes sense for files, but this is applied to entire directories called MyProject.Lib (for example).

Thanks

Upvotes: 0

Views: 188

Answers (1)

Eddie Chen - MSFT
Eddie Chen - MSFT

Reputation: 29976

The global exclusion list is configured by the server, there isn't any way to change it. You can get the detailed list from following path:

%LocalAppData%\Microsoft\Team Foundation\X.0\Configuration\VersionControl\LocalItemExclusions.config

And I can get the same behavior as you with VS2015 Update3, but cannot see this issue with VS2015 Update2.

Upvotes: 1

Related Questions