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
For ASP.NET applications it can be useful to make a request to an application immediately after deployment to bring the application onlin...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
As a team empowered by .NET open source, we’ve always been sensitive to the people, projects, and conferences that make the .NET communit...conference oss team
Previously, I wrote about Publishing to npm Using AppVeyor. This is a similar post, but specifically geared toward publishing an npm pack...AppVeyor npm MyGet
Stuntman is an open source library we developed at RIMdev to make testing user scenarios easier during development time. There are times ...Windows Azure Azure Stuntman OSS
Typically, running a Jekyll site locally for the first time requires a basic knowledge of using the command line. It usually involves a f...jekyll
A picture is worth a thousand words, so I assume a diagram is worth a billion words. Expressing our ideas is important and our blog is an...Jekyll
Before claiming we are in a Renaissance or that it is time for one, we should take the time to understand the meaning of the word and its....NET Community OSS
AppVeyor does not currently provide built-in support for publishing to npm (at least, currently). Instead, we can provide the npm token a...AppVeyor npm
At RIMdev, we are attempting to layer Hypermedia concepts into our APIs. One of these concepts is to have a collection of links to relate...Web API ASP.NET
Transcript Hello my name is Khalid Abuhakmeh and in this video I’ll be presenting an ASP.NET OWIN middleware library designed to eas...video stuntman OSS
On our team TeamCity server we build repositories by default using
build.cmd in the repository root. This has a few advantages.
One advantage is being able to run what TeamCity runs locally. It isn’t perfect – your machine can still be different from the TeamCity build agent. But, it allows running the same commands consistently. This can greatly improve the experience of debugging works on my machine issues.
Another advantage is keeping any complex build setup in the repository. Files in repositories are versioned and follow the familiar pattern of submitting changes via pull requests.
Here’s a simple
build.cmd to get started (this one is useful for Node.js, but can be adapted for your needs!):
@echo Off pushd %~dp0 setlocal :Build call npm install call npm test if %ERRORLEVEL% neq 0 goto BuildFail goto BuildSuccess :BuildFail echo. echo *** BUILD FAILED *** goto End :BuildSuccess echo. echo *** BUILD SUCCEEDED *** goto End :End echo. popd exit /B %ERRORLEVEL%
In this case, the build will run
call npm install and
call npm test in order. You can modify these steps as necessary.
When creating a new build configuration for a project, a template can have
build.cmd usage baked in. This consistency makes it faster and easier to setup a build configuration for new projects.
Team members can assume
build.cmd will be ran for each TeamCity build. Having a consistent build script makes setting up new projects in TeamCity faster and easier, since executing
build.cmd is included as part of a template. And, if a pull request fails to build unexpectedly a quick
git clean -xdf and
./build.cmd can run what the build agent ran!
build.cmd enhances our team development experience by providing consistency.
build.cmd works locally and fails on a TeamCity build agent, this post won’t help you! :-)