files are added anyway under solution control?

[lucamorelli]

Hi,
I added these two entry in the .gitignore file of the solution

**/wwwroot/[Aa]pp/**/*.map
**/wwwroot/[Aa]pp/**/*.js

in the wwwroot/app of my project I deploy the result of the compilation of the typescript files that are under the apprott, and for this reason I don't want that the resulting file are added to the repository any time.
I think the result shoud skip these files inside the wwwroot\app directory of every project in the solution, but when I try to commit the files I see this:

I don't see what is wrong.
Looks like is a tooling problem because if I open the local repository just after I added the solution to source control I see this

The ignores are respected

[babeal]

Source control issues need to be addressed asap please. #18 workaround of using DnxInvisibleFolders no longer works either.

[sayedihashimi]

TFS: 174124
I've added this to our internal TFS, we will reply back here soon.

[ghost]

This bug also applies to other kinds of files like log files:
Steps to reproduce (TFS+VS2015):
Add logs files by making webserver log to web.cong:

1. <httpPlatform processPath="%DNX_PATH%" arguments="%DNX_ARGS%" stdoutLogFile="..\logs\httpplatform-stdout" stdoutLogEnabled="true" startupTimeLimit="3600"/>
2. Add a ".tfignore" file with the following:

logs
*.log
logs\*.*

3. Run the application in VS2015 and notice that the generated log files are added to TFS regardless of the ".tfignore" file.

[webtools-bot]

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!