locked
New assemblyinfo added to cache for every build of unchanged projects RRS feed

  • Question

  • I am part of a team that have been happy users of code contracts for years.

    This week we started using the SQL Server cache on our continuous integration system, to remedy some very long build times due to static analysis. We have something like 1500-2000 projects that all use contracts, but the majority of these projects do not change much, so we thought it was obvious to use caching to save time analyzing these.

    However we are now seeing a peculiar behavior where, for some of the most referenced interface projects, the cache seems to create a new entry in the AssemblyInfo and AssemblyInfoMethods tables. In two days some of the projects have more than 500 entries in these tables, so we're guessing the cache reanalyzes these projects every time and updates the cache.

    Any ideas as to what conditions could cause the cache to misbehave like this?


    Wednesday, January 6, 2016 10:12 PM