Child pages
  • Gaya 8.0 EAP (build 26984) Release Notes

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We've worked hard for a couple of months with our colleagues from the ReSharper team to fix big a large set of bugs in server-side .NET code analysis. Generally, all those bugs could be described as "It see There are no errors (warnings) in Visual Studio, but TeamCity shows me a number of problems in my code."
The reason is - was that the project model , which is an input for code analysis , was incorrectly constructed outside of Visual Studio. In order to fix it this, we now support all set of MSBuild-related features ususally usually used by developers.
Some of them are:

...

Analysis results caches

We also have negative feedback about have also received issue reports about poor performance of code analysis on the server in comparison with ReSharper's work inside Visual Studio. So now all data, (compared to ReSharper). To mitigate this, all data produced by code analysis which could be used reused in future builds on the same build agent , is stored outside of the checkout directory (by default) and cleared as ususal TeamCity build agent's caches datais cleaned up together with other agent caches.

Remove build feature

Other improvements

...