Rothi's Blog

In our current project we try to use the MOQ framework in order to mock away database accesss in our business logic tests. I was testing some business logic where the executed method would compare different objects and aggregations of objects with each other in order to behave one way or the other. The method builds intersections of collections using the Except extension method and stores intermediate values in lists using the Equals method. Some first tests were successful where the database wasn't mocked. Introducing mocks made me bang my head on the table because of two reasons at least: Getting used to the "over-Lambda'd" syntax of MOQ and trying to guess what was really meant on the MOQ QuickStart page . The documentation is rather sparse and a lot guess work and learning-by-pain seems to be the best way to get along. At least after some time you get along with the syntax and even start to like it. Lists don't behave like they behaved before. WTF! Compare

On my current project I try to learn new web technologies: HTML5, CSS3, JavaScript, jQuery etc. When dealing with the different versions of JavaScript-libraries I hit " git " the first time. Almost any library seems to be published using GitHub nowadays. Since we needed a VCS I had the option to take the old Subversion and deal with that system or try the new Git system. Reading about it I was getting more and more curious about it. I liked the idea about a repository on the internet like GitHub , which would give us the opportunity to work in shared teams. So I installed git for testing and made my first tries. After several hours of trying to get connected to GitHub I had to abandon this. I was (and am still) very disappointed: Of course I'm behind a firewall, of course we use a proxy at the company I work at. I tried different hacks about telling git the proxy server etc. Which is by the way a very bad solution since this is stored in a file on your home directory ca

I'm writing this blog entry after my experience when trying to set up a scrum-like process at my current company. I recently stopped my efforts and want to discuss with you how you estimate: When is the time you must admit you failed or simply when is the time to stop fighting? But back to history: After some painful project failures last year I enganged a little bit into agile software development and read a lot. Like many others I was immediately fascinated by the idea and concept (and I am still). So my boss asked me to take four colleagues for three months to evaluate different processes and develop a software development process fitting our department and company. We developed what's called a "Scrumbut" - Scrum with some adoptions to local structures and a little bit of more focus on planning than in "classic Scrum". Well done, we reached our goal at the end of March and then were heading for the first project to show how the process works. I was enga

Yesterday I attended the Keynotes to the Mix developer Conference in Las Vegas via Live Stream. They showed quite amazing stuff there using HTML5 with hardware acceleration in IE9. Folks at Microsoft really seemed to scorn Google's Chrome - showed up several Demos where Google Chrome was lame and IE9 kicked ass. Was quite funny but that's not what made me write this. I attended the keynotes to see where the Microsoft trip goes to. At my current company Krones I have the task to propose a graphic framework for the future. There are lots of native applications, some using Win Forms, some even using old VB. Others are ASP.NET applications and run in the browser only. We'll have to port these applications and find a common graphic plattform for them: Or almost common. Some time ago I hit the PRISM framework making it possible to have one architecture for your WPF and Silverlight applications under the hood. I made some small steps with Silverlight 3 in 2009 and was quite am