• Continuous Integration,  DotNet,  Software Engineering

    Dveloper Week / Dotnet Developer Conference 2013

    Herzlichen Dank an alle die Teil in mein Vortrag wahrend Developer Week / Dotnet Developer Conference 2013 in Nürnberg genommen haben! Das war eine Hervorragende Stunde! Ich hoffe Ihr etwas über „Continuous Integration in .NET“ gelernt habt. Herrlichen Dank an Organisatoren für die Einladung. Danke an Kollegen Referenten. Danke an alle 1500 (?!) DWX 2013 Teilnehmer! Und als Bonus – CiInDotNet_Dwx

  • Continuous Integration,  DotNet

    I will be speaking at .NET Developer Conference in Nuremberg, Germany

    I’m happy to announce that I will be speaking about Continuous Integration in .NET at .NET Developer Conference (DCC) in Nuremberg, Germany. The .NET Developer Conference is a part of Developer Week (DWX) that combines 3 events WDC (Web Developer Conference), MDC (Mobile Developer Conference) and DDC. It takes place from 24th to 27th June 2013. My session is on Monday the 24th. More information on the DWX 2013, the program and speakers are available at www.developer-week.de. You are very welcome! PS. I have a discount code for all my blog readers – if you want one please drop me a line!

  • Continuous Integration,  DotNet

    I will be speaking at MTS 2012

    MTS or Microsoft Technology Summit is the biggest technical conference Microsoft in Poland. It is the place where few thounsend developers, IT specialists and business people meet to get the latest informations from Microsoft and to talk about things that are relevant. This year was invited to MTS to give a talk about continuous integration. Let’s meet at MTS 2012!

  • Continuous Integration,  DotNet

    More on "Continuous Integration in .NET"

    I’ve recently got the sales report from Manning about my book “Continuous Integration in .NET”. I’m very happy to report it sells quite well! And speaking about the book. My friend Mateusz Łoskot send me an excerpt from the ACCU discussion board discussing my book. Here it is: > Interesting you mention the Manning books on Dependency Injection and Continuous Integration… is there really a whole books-worth of stuff in each of those topics?? If you are in the .NET world then then ‘Continuous Integration in .NET’ is really worth the time invested. It covers most of commonly used tools (CC.NET, MSBuild & Team System, TeamCity). Goes over integration of…

  • Continuous Integration,  DotNet,  MSBuild

    Visual Studio 2010 Professional and Hudson / Jenkins CI and FxCop

      Visual Studio 2010 Premium and Ultimate do have the code analysis feature build in. What this feature does is static code analysis of your source code (or IL to be specific). Unfortunately the Professional edition lacks the build in integration (no Analysis tab in the project properties). Here is a way to easily integrate Visual Studio 2010 Professional with FxCop. FxCop is a standalone Code Analysis version that comes together with “Microsoft Windows SDK for Windows 7 and .NET Framework 4 Version 7.1”. Actually if you download and install the SDK you will get the FxCop installer in %ProgramFiles%\Microsoft SDKs\Windows\v7.1\Bin\FXCop. You will have to install it from there (yeah…

  • Continuous Integration,  DotNet

    Continuous Integration in .NET – dead tree edition

    Finally it happened. I’ve just got my author copies of “Continuous Integration in .NET” the book I coauthored. I’m very, very happy because it was a long journey and finally it happened. My first book is out. I would like to thank all the people who helped at Manning and outside. I was considering writing a longer post about the process, the ups and the downs, but I decided not to. I might return to that thought later. In a mean time if you are considering coauthoring a book with someone you don’t know think twice. If you are considering writing something together with Craig Berntson and want to know…

  • Continuous Integration,  DotNet

    Hudson Continuous Integration LED message board monitor

    Knowing the state of the build is one of the most important aspects of Continuous Integration. Team should get the information about the problems with he build as soon as possible. If the quality of source code degrades rendering the build to fail team, should jump in and fix the problem. The most popular group of tools that make the swift reaction possible are the tray notifiers. Small programs that reside somewhere in the corner of the screen and show one of the 3 states the build server is ever in: 1. Building 2. Failed 3. Yet another successful build! Oh, and well… not working (if the CI server is…

  • Continuous Integration

    Speaking about continuous integration

    I will be speaking on Wednesday (20.01.2010) in Krakow, Poland at the Karkow .NET Developers Group meeting. The session is about Continuous Integration in .NET. So if you like hear what I have to say about CI meet me at ABB ISDC, Pałac Pugetow, ul. Starowislna 13, Krakow at 18:30. I believe the attendance is free but registration is required. See you in Krakow!

  • Continuous Integration,  Windows

    Selenium RC and FitNesse as a service on Windows Server 2008

    If you are working in a team or running a continuous integration process the most comfortable way to run tools like Selenum RC Server or FitNesse is to install them as a windows service. I was doing this earlier on my old Windows Server 2003 by issuing the  instsrv.exe (to install a service) on srvany.exe (to run anything) – both from Windows Resource Kit. I had to edit the registry to provide what exactly do I wanted to run (java –jar selenium-server.jar or java –jar fitnesse.jar). But there is no Windows Resource Kit for 2008. You might use the sc.exe and get the old srvany.exe (with compatibility issues according to…

  • Continuous Integration,  Windows

    How to make CruiseControl.NET accept SSL certificate under Windows Server 2008?

    If you are running CruiseControl.NET under the Local System account and your SVN server certificate was issued by yourself (or by VisualSVN Server) you will quickly run into trouble. Normally if you run any command on your repository you will get this information: C:\Program Files\svn\bin>svn log https://your_server/svn/your_repository/trunk –username username –password password Error validating server certificate for ‘https://your_server:443′: – The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! – The certificate hostname does not match. Certificate information: – Hostname: your_server – Valid: from Sat, 26 Sep 2009 17:24:27 GMT until Tue, 24 Sep 2019 17:24:27 GMT – Issuer: your_server – Fingerprint: 24:8e:f6:ba:c7:a6:3f:69:32:c0:21:92:64:44:62:fe:2c:bb:b4:69 (R)eject,…