When comparing TeamCity vs ReSharper, the Slant community recommends TeamCity for most people. In the question“What are the best .net tools?” TeamCity is ranked 18th while ReSharper is ranked 28th. The most important reason people chose TeamCity is:
TeamCity has different installation packages for different operating systems. All the user needs to do is download the correct one and run it.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy installation
TeamCity has different installation packages for different operating systems. All the user needs to do is download the correct one and run it.
Pro Cross-platform build support
The fact that it is based on Java does not hinder TeamCity's ability to support different build environments. TeamCity in fact supports a large number of languages and tools for each of those languages (build runners and test frameworks).
Some of the languages/platforms that are supported include: Ruby, .NET, Java.
Pro Brilliant interface
The user interface of TeamCity is clear, well thought out and the dashboard is highly customizable.
Pro Supports build chains
The user can easily compose dependencies between builds by adding snapshot and artifact dependencies, all on the one screen. All output of upstream builds is available to downstream builds. Triggering sets off the entire build chain and supports re-running of the portions of the chain that failed.
Pro Well documented
Pro Extensible
TeamCity offers well defined APIs for extending, as well as a REST interface.
Pro Testing support
TeamCity supports both MSTest and NUnit (which is open source) to run tests.
Pro Best choice for .NET
Seems to be the best choice for .NET applications, but to be honest: if you stray from the default settings you will be in a lot of pain most of the time.
Pro Testing tools are handy
Pro Ctrl + T is useful look of classes, enums, interfaces, etc
Pro Refactoring tools are powerful
Extract interfaces, generate constructors, rename namespaces, create equality statements, create ToString() summaries, etc.
Pro Extremely useful when reading code written by others
ReSharper has a built-in "go to implementation" feature which takes you to the body of the implementation of a method from an interface. This makes it easy to read code written by other people simply by going over the interfaces and using this feature to quickly find the implementation of a particular method.
Cons
Con Expensive
TeamCity has a free tier which includes a maximum of 100 build configurations and up to 3 build agents. If you want to add 10 more configurations and 1 more agent, it will cost $299; unless you choose to buy an enterprise license which starts at $1999.
Con Poor quality plugins
At least some of them do not work, probably because they're not updated to more recent TeamCity versions.
Con Inter-branch merges trigger emails to unrelated committers
Whenever an inter-branch merge occurs, TeamCity pulls up the first parent of the merge commit and sends them an e-mail. However, this sort of information would be more useful to the merge author.
Con Increases build (compile) time
Adds a considerable time onto building my Xamarin Forms project.
Con It can mangle Visual Studio settings
Occasionally Visual Studio and Resharper settings can get into a tug of war. Features can disappear, for example, Intellisense can vanish, and you're often resetting options in hopes of getting yourself back to a working IDE.
Con Licencing cost and T&Cs
The license T&Cs are somewhat harsh. The yearly license gets you a year's worth of updates, but you don't get major version release within that window. Instead, you're downgraded to the previous major version that you bought the license on.
Con Performance leaves something to be desired
The performance has been an issue for years, and many developers who have tried this tool gave up because of the performance hit running it. You may often find the tool to make Visual Studio slow down to almost an intolerable level.