Over the last few weeks we have made a great deal of improvements in .NET inspections support. As a result .NET Inspections (powered by JetBrains ReSharper) and FxCop inspections runners produce much more clear results. In case you missed, some time ago we announced new .NET inspections runner based on ReSharper inspections engine, and we already received feedback on it. Thanks to our EAP users we were able to fix a number of serious problems: - LINQ usages are marked as unresolved symbols; - TW-18724 NUnit attributes usages (and all External Annotations); - TW-18730 Usages of resources in WP

"I see dead code" - .NET developers all over the world know this slogan due to incredible code analysis feature provided by JetBrains ReSharper. One of the most wanted TeamCity features was to have .NET inspections results right on build server. Starting with the latest EAP you have it! The only thing you need to do to get all the benefits of ReSharper's analysis right in TeamCity is to add Inspections (.NET) build runner as a build step to your build configuration. Configuration is quite easy, so let's just take a look at how the results look when this runner is configured - you can find

In the latest TeamCity 6.0 EAP we've added new feature to Visual Studio add-in. Now it is tightly integrated with another popular JetBrains product – ReSharper! So if you have both ReSharper 5.0 (or later) and TeamCity add-in installed, you gain the following benefits: From the add-in's Failed Tests tool window you can navigate to source code of a failed test. From the same tool window, you can re-run tests failed in a TeamCity build locally with ReSharper. Note, that by "tests" we mean all kinds of tests supported by TeamCity and ReSharper. This feature is just the beginning, we plan to