Large check-in with nuget packages does not check-in


We have decided to check-in our nuget packages (after nuget been down for a few hours). And check-in of 170Mb of dll's did not want to go in.

VS became very unresponsive and deadly slow as soon as you add all these files into pending changes. And attempt to actually check-in also made no good - progress bar is spinning, but nothing is happening, eventually (after an hour) check-in is rejected with message that some policies were not satisfied (but does not say which ones -(.

As soon as I disable Stylecop check-in policy, everything gets checked-in within a minute with no slow-downs.

VS2013 with Update 1. TFS2010.

Many thanks!
Closed Jul 22, 2015 at 1:24 PM by LockTar
Large projects have many rules to check. Performance should now be better but is difficult to manage. What is a 'large' project?


LockTar wrote Feb 1, 2014 at 1:37 PM

A large number of files could give problems to the checkin policy. This is because the policy will loop threw the files and try find the issues. Do you have more information of how I can reproduce this issues. Could you test your problem by placing your code in "Excluded changes" in your pending changes window. The plugin would not check those files. After that you can "Include" all or a part of the files. Maybe some particulair files give problems to the policy?


trailmax wrote Feb 1, 2014 at 3:51 PM

Reproduce the issue? Easy! Get a project with some number of packages. I've used MVC5 project with 160Mb worth of packages. Add all the packages to source control and see this in action.

This seems to be an issue with TFS2010 only. Just checked-in a bunch of packages into other project in on TFS2013 and no issues.

LockTar wrote Feb 1, 2014 at 4:58 PM

Oke thank you for the extra information. It are NuGet packages that you use right? Not packages that you created yourself right?
the extra information about the TFS server version is important information. I could test This on my work because there we still have 2010.

trailmax wrote Feb 2, 2014 at 12:09 AM

Yes, they are nuget packages that are part of the project, downloaded from nuget.org. Files in __/packages/*__ folder - load of dlls with xml files along with some other crap people put in their nugets.

I think what threw off stylecop policy is presence of source code (actual *.cs) files inside of these packages. For example nuget for "TimePeriod" contains source code.