.NET

The .NET Core development platform is the next wave of .NET ecosystem evolution which brings cross-platform targets for your existing or new products. Microsoft ships .NET Core SDK packages with a runtime for supported platforms and command line tools (.NET CLI) to build, test, and pack such projects. The .NET Core support plugin for TeamCity aims to bring streamline support for .NET Core CLI by providing .NET Core build steps, CLI detection on the build agents, and auto-discovery of build steps in your repository. Installation The plugin is available for download from the TeamCity plugin

A large number of TeamCity users are working with Microsoft technologies and platforms such as Visual Studio Online and Azure, both fantastic tools in their respective areas. We are really excited to announce several new integration points between TeamCity and these tools! Special TeamCity Offer for MSDN Subscribers Today we are launching a special offer in partnership with Microsoft. All MSDN subscribers are eligible for a 50% discount on new TeamCity Enterprise licenses. Visit the MSDN special offers page to see the details and apply for the discount. This is the first time TeamCity off

Many teams are working with Visual Studio Online (VSO), a hosted Team Foundation Server that provides source control and issue tracking as a cloud service. While VSO comes with a build server as well, lots of developers prefer to use TeamCity for their continuous integration story because of its advanced features to automatically run builds for feature branches,  automatic merge and many others. TeamCity supports building projects that are hosted on Visual Studio Online, the only thing we have to do is add a VCS root to our build configurations. Depending on the version control system used

UPDATED: Join us Tuesday, June 10th, 14:00 – 15:00 GMT (10:00 AM – 11:00 PM EDT) for our free live webinar, .NET Code Coverage for Continuous Integration using TeamCity and dotCover, with Maarten Balliauw. How much of our code is being covered by our unit tests? Are there areas we are not testing? By capturing code coverage data during a test run, we can analyze which areas of our applications are well-tested and which ones require additional tests to be written. And where better to capture code coverage information than on our build server? In this webinar we will use dotCover to collect co

Deploying ASP.NET applications can be done in a multitude of ways. Some build the application on a workstation and then xcopy it over to the target server. Some use a build server, download the artifacts, change the configuration files and xcopy those over to the server. The issue with that is something bad creeps in: deployments become unpredictable. Using the premise of Continuous Delivery, we can make deployments predictable. Automating all the steps will ensure that deployments can always be done and reproduced, ideally by going through a pipeline of environments. TeamCity may ha

When working with NuGet we can make use of package restore. The concept is simple: instead of committing packages that we depend on to source control, we only commit the list of dependencies we need and download the assemblies during build. In TeamCity, package restore is supported in various ways. We can use the NuGet.targets file (NuGet v2.6 and earlier) or run nuget restore from the command line (v2.7). TeamCity has a build runner which makes setting up package restore a breeze: the NuGet Installer. NuGet Installer The NuGet Installer build runner will make sure all package dependencie

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

New TeamCity 7.0 EAP build is ready and waiting for you to try! We have improved features introduced in the first EAP build, and of course we've got some completely new stuff. .NET Inspections runner Yes, it's finally here and it's based on powerful ReSharper code analysis engine! Now you can run .NET inspections and see the results right in TeamCity. Global Maven settings Previously you could specify path to alternative user settings file (equivalent to Maven command line option -s or --settings) in build configuration.  Now you can define these settings xml files globally in Server Configu

Today I'd like to share with you a plugin for TeamCity 6.5 that provides support for NuGet, the open source developer focused package management system for the .NET platform. What does the plugin bring? NuGet Packages Installer The plugin adds dedicated build runner that allows you to: Install NuGet packages without having to check them in to the version control, which comes in handy especially when using a DVCS, like Mercurial or Git. The problem and a workaround is also covered in David Ebbo post. Automatically update package dependencies to the most recent ones (optionally). Note, tha

New TeamCity 6.0 EAP build is now available with Gradle support described in previous post and several new features and major improvements: Improved upgrade procedure. First of all, we have reworked the upgrade procedure. Though it already was quite painless, we've made it more explicit and smooth. Usually, a typical TeamCity upgrade requires conversion of database and configuration files. Since, previously this was performed automatically, it could be not clear what and why had happened. Now, when TeamCity decides that the data conversion is required, it asks for confirmation from server a

Have you already tried multiple runners in latest TeamCity 6.0 EAP builds? If you have, there's no need to repeat that now you can split the build procedure into steps and add as many build runners to be invoked sequentially as you need, for instance, call a NAnt script before compiling VS solutions. Having this approach implemented, we decided to review existing .NET runners in TeamCity. As you know, TeamCity provides bundled support of NUnit and MSTest. In previous versions you could configure running such tests within MSBuild and VS.Solution build runners. That was reasonably good and ha