locked
Opening solutions connected to TFS Preview very slow RRS feed

  • Question

  • I've got a solution which is in source control in TFS preview. When I open the solution in Visual Studio it takes several minutes to open. The message in the status bar is saying 'Updating source control status...'. Is anybody else also experiencing these problems? Anybody got a solution for it?

    Monday, February 27, 2012 7:56 PM

Answers

  • Here is the update. It looks like there is a known bug with the Nuget product that it calls workspace.PendAdd for every item in the solution, everytime the solution is opened. That is fixed in the next version of Nuget which is Nuget 1.7 and it should release any day now.

    Thanks for reporting this to us.

    Thursday, March 8, 2012 8:02 PM

All replies

  • Hi Koen,

    We would like to dig in further on why you are getting slow performance. Can you provide your TFS URL and time when you experience slow performance? Do you see this performance every time you open solution in VS? Also how big the solution is? Hoy many project does it have?

    Regards,

    Anjana

    Tuesday, February 28, 2012 4:42 PM
  •  Are you still seeing the issue?
    Wednesday, February 29, 2012 5:56 PM
  • I had the problems about 2 days ago, and some days before that. My TFS url is willemse.tfspreview.com. I can't reproduce this issue currently, since I had to reinstall my machine. As soon as I've got Visual Studio installed again I will try and update the thread.

    Wednesday, February 29, 2012 6:00 PM
  • Do monitor the time when you see the issue. This will help us in filtering the data in the log files.
    Thursday, March 1, 2012 3:32 PM
  • I've the same problem with tfs preview when opening a solution which is under source control.

    If you want to dig into your logfiles, take the timestamp minus 10 minutes of this posting and "a3sbag" as the prefix for tfspreview.com ; )

    with Fiddler, I can see several calls like this:

    POST /DefaultCollection/VersionControl/v1.0/repository.asmx HTTP/1.1

    obviuosly for each file in the packages folder!

    the output window schows the following:

    The item $/xxxxxx/packages already exists.
    The item $/xxxxxx/packages/repositories.config already exists.
    The item $/xxxxxx/packages/AspNetMvc.4.0.20126.16343 already exists.
    The item $/xxxxxx/packages/AspNetMvc.4.0.20126.16343/AspNetMvc.4.0.20126.16343.nupkg already exists.
    The item $/xxxxxx/packages/AspNetMvc.4.0.20126.16343/lib/net40 already exists.
    The item $/xxxxxx/packages/AspNetMvc.4.0.20126.16343/lib/net40/System.Web.Mvc.dll already exists.
    The item $/xxxxxx/packages/AspNetMvc.4.0.20126.16343/lib/net40 already exists.
    The item $/xxxxxx/packages/AspNetMvc.4.0.20126.16343/lib/net40/System.Web.Mvc.xml already exists.
    The item $/xxxxxx/packages/AspNetRazor.Core.2.0.20126.16343 already exists.
    The item $/xxxxxx/packages/AspNetRazor.Core.2.0.20126.16343/AspNetRazor.Core.2.0.20126.16343.nupkg already exists.
    The item $/xxxxxx/packages/AspNetRazor.Core.2.0.20126.16343/lib/net40 already exists.
    The item $/xxxxxx/packages/AspNetRazor.Core.2.0.20126.16343/lib/net40/System.Web.Razor.dll already exists.
    The item $/xxxxxx/packages/AspNetRazor.Core.2.0.20126.16343/lib/net40 already exists.
    The item $/xxxxxx/packages/AspNetRazor.Core.2.0.20126.16343/lib/net40/System.Web.Razor.xml already exists.
    The item $/xxxxxx/packages/AspNetRazor.Core.2.0.20126.16343/tools already exists.
    The item $/xxxxxx/packages/AspNetRazor.Core.2.0.20126.16343/tools/Install.ps1 already exists.
    The item $/xxxxxx/packages/AspNetRazor.Core.2.0.20126.16343/tools already exists.
    and so on....

    Friday, March 2, 2012 11:25 AM
  • me once again:

    I think that's the same issue as here:

    http://social.msdn.microsoft.com/Forums/sk/tfsversioncontrol/thread/e133c954-ff7b-4523-9537-ace5e808b118

    I removed the "packages" folder completely and the issue is gone!!

    what hapens here? one call to this service needs about one second.

    Friday, March 2, 2012 2:08 PM
  • What is the package folder? Are all the assembly's are check in source control?
    Friday, March 2, 2012 4:19 PM
  • The packages folder is created by the Visual Studio when I create a new project.

    It contains binaries and *.nupkg files. The folders name of each package represents the name and the version.

    like this:

    packages/EntityFramework.4.1.10331.0
    packages/EntityFramework.4.1.10331.0/lib/EntityFramework.dll
    packages/EntityFramework.4.1.10331.0/lib/EntityFramework.xml
    packages/EntityFramework.4.1.10331.0/EntityFramework.4.1.10331.0.nupkg
    packages/jQuery.1.5.1/jQuery.1.5.1.nupkg
    packages/jQuery.1.5.1/Content/Scripts/jquery-1.5.1.js
    packages/jQuery.1.5.1/Content/Scripts/jquery-1.5.1.min.js
    .... and so on

    And - yes - everything is checked in.


    Saturday, March 3, 2012 9:34 AM
  • In that case, if you open the solution first time then it will download all these files and assembly in the package which will depend on the size of the assembly and package that will contribute to the slowness.

    Monday, March 5, 2012 5:51 PM
  • No, that's not the case.

    Everytime, when I open the solution the tfs-services are called and Visual Studio is not responding during this time.
    There are no downloads.

    Tuesday, March 6, 2012 8:30 AM
  • For me the same thing was happening. After seeing the previous comments, I remember seeing the same behavior. The nuget packages folder is automatically checked in. When opening the solutions (everytime) it's going to do a lot with these files, eventhough they are up to date and nothing has to be downloaded and this takes several minutes to complete.

    Next to that, when opening the solution, it should not download the latest version of course.

    Tuesday, March 6, 2012 8:33 AM
  • Thanks for confirming this. It looks like nuget package is the common factor here. Let me setup a repro with nuget package and dig in further. I will update this thread with my findings.

    Regards,

    Anjana

    Tuesday, March 6, 2012 2:42 PM
  • Here is the update. It looks like there is a known bug with the Nuget product that it calls workspace.PendAdd for every item in the solution, everytime the solution is opened. That is fixed in the next version of Nuget which is Nuget 1.7 and it should release any day now.

    Thanks for reporting this to us.

    Thursday, March 8, 2012 8:02 PM
  • great news! thanks a lot ;)

    looking forward to the next version of Nuget

    Thursday, March 8, 2012 8:25 PM