Localization is great
-
We are running a Jenkins service for automatically building our projects and also our setups (with a call to Visual Studio's command line). Now, one of the setups failed. I scrutinized the output for finding the reason - but no, everything was marked fine. At least I thought so when I searched for "Fehler" (German word for "error"), since the entries were like e.g. "51 erfolgreich, Fehler bei 0," or "0 Fehler, 1 Warnungen" just everywhere. Why did it fail then? Well, I tried the a search for "error" - and voilà here it is: "error MSB3104: Die referenzierte <Path-to-some\Other.dll>-Assembly wurde nicht gefunden..." The error message is available in a nice mixture of German and English. Great idea: if something goes wrong, use the English term "error", otherwise use German.
-
We are running a Jenkins service for automatically building our projects and also our setups (with a call to Visual Studio's command line). Now, one of the setups failed. I scrutinized the output for finding the reason - but no, everything was marked fine. At least I thought so when I searched for "Fehler" (German word for "error"), since the entries were like e.g. "51 erfolgreich, Fehler bei 0," or "0 Fehler, 1 Warnungen" just everywhere. Why did it fail then? Well, I tried the a search for "error" - and voilà here it is: "error MSB3104: Die referenzierte <Path-to-some\Other.dll>-Assembly wurde nicht gefunden..." The error message is available in a nice mixture of German and English. Great idea: if something goes wrong, use the English term "error", otherwise use German.
:doh: OT (Sorta) I am going to be removing CC.NET from my build server and reinstalling Jenkins, then setting up a reverse proxy in IIS to point a URL at the Jenkins instance. I do not like CC.NET very much, but I do like Jenkins.
Bob Dole
The internet is a great way to get on the net.
:doh: 2.0.82.7292 SP6a