Setup: Windows – .NET 4.5, Linux – Mono 3, Mint 17 (based on Ubuntu 14). I need to build and test .NET application from command line and on CI server.
Sample solution can be downloaded from here https://github.com/mchudinov/BuildingTesting. Solution is compatible with MonoDevelop 5, Xamarin Studio 5 and Visual Studio 2012,2013,2015.
1. Building in command line
There are two standard command line building tools for .NET: MSBuild on Windows and xbuild on Linux/Mono. xbuild build files are compatible (with some exceptions) with MSBuild files.
We need at least 4 simple steps (targets as they called in MSBuild terminology) to build a .NET solution:
Some days ago I have been at Norwegian Development Conference in Oslo city (http://www.ndcoslo.com/). There were a couple of very good sessions about Scrum. I talked to people after those sessions, talked to Scrum Masters, developers, product owners about they experiences with Scrum. I figured out some typical mistakes that Scrum teams make. All these mistakes have actually the same root: Scrum practitioners forget about the reasons why we do Scrum.
The reason why Scrum invented in Toyota is to implement some principle of Toyota Production System. Continue reading →
I want to mock some methods from an external dependency class without executing the original constructor for this external class. This external class is from somewhere else, imported to our project by composer for example. Continue reading →
When PEAR installs itself on Windows it places pear.ini file in the system folder c:\Windows by default. Which sometimes needs to be changed after all. And sometimes it is not possible for some reasons (not sure why, probably a bug in PEAR installation scripts) to change this location during the installation. Then we need to change this location when PEAR is already installed and in use. Continue reading →
There was a PEAR installer go-pear.bat that referred to ./PEAR/go-pear.phar in php versions prior to 5.3 on Windows. But since version 5.3 this installer is absent. Strange enough but official PEAR installation guide still refers to the absent go-pear.bat file. But then it writes about update of PEAR installation by requesting a new go-pear.phar and that is what we should actually do at the beginning. Continue reading →