At Ritter Insurance Marketing we value our peers and other organizations in the overall software community. We believe in the power of c...OSS
Software development is a funny thing. As I develop my skills, I begin to form an idea of what’s right and wrong, what’s up and down. Thi...elasticsearch
At Ritter Insurance Marketing we have a number of repositories, each with separate continuous integration builds. This is a base setup f....NET Cake AppVeyor
In the whirlwind that is modern web development, I thought it would be a great idea to revisit one of the fundamental parts that make the...HTML Web
Picture a scenario where you want to page a large dataset and your LINQ statement has several Include-calls. The first few pages load fai....NET SQL Server LINQ
Setting up a local server comes in many flavours today. My goto was the Apache vhost.conf/hosts combo, now to load something quickly - Gu...gulp
[Hacktoberfest 2017][hacktoberfest] is upon us and now is a great opportunity to contribute to open source and the community as a whole. ...OSS
TL;DR Using ExecuteReader against SQL Server with a query using for xml or for json causes data to be chunked. A single call to ExecuteR....NET .NET Core 2.0 JSON XML SQL Server
At Ritter Insurance Marketing, we continue to invest heavily in Web APIs primarily built on top of ASP.NET Web API 2. To supplement our A...asp.net WebAPI REST
If you CSS, you’re familiar with the browser -prefix. Chrome and Safari have -webkit, -moz for Firefox/Mozilla, and -ms for Edge. As brow...css
We decided not to use Material Design (#reasons) while re-developing our core application suite, although i really miss MD’s micro-intera...UI Sass Semantic UI
Sometimes it’s useful to ensure a project works with multiple versions of runtimes. In the following example, multiple versions of Node.j...AppVeyor
Update October 17, 2017 This doesn’t work with environment deployments, as this needs to run after the deployment has completed. See htt...AppVeyor
https://xkcd.com/1597/ While I generally don’t do that, here’s what I currently do: Setting up a repository locally Using Stuntman as...GitHub
.NET Core is a cross-platform runtime, and if you play your developer cards right, you can take advantage of running your application on Windows, macOS, and Linux. We enjoy writing many open source projects. Sometimes we opt to use our internal TeamCity CI server and other times we use Travis CI for more transparency. This post will help you get your .NET Core application building in Travis CI by showing you the files you need in your publicly accessible Git repository.
You need a build script to the root of our repository for Travis CI to execute. It is quite simple.
#!/usr/bin/env bash dotnet restore && dotnet build
You can add additional steps to the
build.sh to run tests, but this is the simplest command you need.
.travis.yml is used by the service to construct your build environment. Add this to the root of your repository.
language: csharp dist: trusty sudo: required mono: none dotnet: 1.0.1 script: - ./build.sh --quiet verify
We do a few things in the configuration file:
mono; we are running .NET Core now
Note, we could forgo calling our
build.sh file and put the calls to
dotnet in the script section of our configuration. We chose not to in this case. The Trusty version of Ubuntu is 14.04. Ubuntu 16.04 was released back in April of 2016, but Travis CI does not support it yet. Travis CI default distribution is 12.04, which is not supported by the .NET Core installer.
After adding the files, you can follow this basic tutorial to setting up your project. If everything goes right, you should have a successful build on Travis CI. It really takes very little effort and will help your contributors know if they broke the application.