Visual studio feeds

All Visual Studio blogs in one place


Enter your email address:

Delivered by FeedBurner

Increase your website traffic with



Anti-spam: How many eyes has a typical person?

Follow us on FB


Song of the Day: Press the Buzzer

AddThis Social Bookmark Button
Press the Buzzer is based on the infamous Milgram Experiment.  This brilliant song captures the entire essence of the experiment and the fall out from it, without ever losing its compelling folk rock rhythm. Like nearly all her music, this one … Continue reading → For the complete article and hyperlinks, please visit my blog at

Xamarin.Forms: Incremental Search

AddThis Social Bookmark Button
I recently posted about obtaining data for purposes of creating demonstration programs.   That actually was written in service to today’s post, which will use that data to create a list of “people” and then allow you to search incrementally, as shown in … Continue reading → For the complete article and hyperlinks, please visit my blog at

The Single Responsibility Principle under the microscope

AddThis Social Bookmark Button
Originally posted on:’s equally important and mysterious: the Single Responsibility Principle (SRP). And even though its originator Robert C. Martin tried to explain it again, I feel there is something lacking. Some concreteness, some tangibility. First the definition of the SRP in Martin’s own words: “The Single Responsibility Principle (SRP) states that each software module should have one and only one reason to change.” This is more informative than Wikipedia’s tautology: “In object-oriented programming, the single responsibility principle states that every class should have responsibility over a single part of the functionality provided by
the software, and that responsibility should be entirely encapsulated by the class.” But still… Martin’s definition is not crystal clear. It leaves much room for interpretation during TDD refactoring or code reviews. Even he admits this: “However it begs the question: What defines a reason to change?” To improve on this, he developed the notion of a “responsibility owner” as I’d call it: “When you write a software module, you want to make sure that when changes are requested, those changes can only originate from a single person, or rather, a single tightly coupled group of people representing...(Read whole news on source site)

2015: An Interesting Year for OpenStack - Tesora

AddThis Social Bookmark Button
2015: An Interesting Year for OpenStack - Tesora

This year, he expects VMware to gain a larger following than Red Hat by
virtue of the VMware Integrated OpenStack program, which shows that the
company realizes that the hypervisor is now a commodity and the real
action going forward will happen on the control plane. As well, he says
the OpenStack community will accept Debian Linux as the default host
operating environment considering it is the only mainstream,
vendor-neutral distribution left, and developers will see the folly of
pulling untested
applications from upstream environments into main
production, also known as “running the trunk.”...(Read whole news on source site)