The strange subfolder "DTAR_08E86330_4835_4B5C_9E5A_61F37AE1A077_DTAR" created in the VS2015 UWP solutions folder

Question

I saw this empty subdirectory DTAR_08E86330_4835_4B5C_9E5A_61F37AE1A077_DTAR , created several times in different solutions (all UWP) and even in the default project "Blank App (Universal Windows)", the problem is that I can not play it intentionally - sooner or later, it just created, but I don’t know why and why.

Does anyone have any clues?

PS. Here is my configuration, if it is important:

Microsoft Visual Studio 2015 Version 14.0.23107.0 D14REL
Microsoft .NET Framework 4.6.01028
Visual Basic 2015 00322-20000-00000-AA447
Visual C # 2015 00322-20000-00000-AA447
Visual C ++ 2015 00322-20000-00000-AA447
Windows Phone SDK 8.0 - ENU 00322-20000-00000-AA447
Application Insights Tools for Visual Studio 1.0
ASP.NET and Web Tools 14.0.20626.0
Web Platforms and Tools ASP.NET 2013 5.2.30624.0
Common Azure 1.5 Tools
GenerateUnitTest 1.0
GitHub.VisualStudio 1.0
JetBrains ReSharper Ultimate 10 EAP 4 Build 104.0.20151009.190534-EAP4
Microsoft Azure for Mobile Services 1.4
NuGet 3.2.0 Package Manager
P4VS - Perforce Plugin for Visual Studio 2015.1.105.4164
Pre-Analytical Document Analyzer 1.2
SQL Server Data Tools 14.0.50616.0
Visual Studio Tools for Universal Windows Applications 14.0.23309.00 d14oob

Answer 1

It seems that (finally) is fixed in the recent Visual Studio Update 3 RC (works for me at least).

There is also another “more permanent” workaround from EricStj - MSFT (copied from its comment on the corresponding release here ) for those who would rather wait for the RTM version of this update and should skip the current RC version:

The fix did not get into Update 2. It should appear in Update 3. To work around this file, replace this file with " C: \ Program Files (x86) \ Assembly Links \ Microsoft \ Framework.NETCore \ v5.0 \ GlobalDTARSettings .proj "with the version from here: https://gist.github.com/ericstj/b40dd3846c3faec5ea1ba55fce64d1f8 .

Answer 2

In fact, there is a problem filed on Connect , which is currently being addressed by Microsoft. So in some room there is a reasonable suspicion that this is a Visual Studio 2015 error.

There is also a workaround:

Posted by DaisyDave on 12/15/2015 at 2:40 a.m.
Opening solutions from the IDE stops the appearance of these folders.

Answer 3

In general, I open solutions from Windows Explorer, and not from Visual Studio. If you look like me, the Connect problem mentioned in Andreas's answer has a second solution to open the solution from Windows Explorer:

Posted by Dee Key on 3/4/2016 at 11:22 AM
In Windows Explorer, right-click the solution file and open it using Visual Studio 2015.