sfeldman.NET

If you have tried to build a web interface that would work for most of browsers and variety of devices, you’ll appreciate Twitter Bootstrap project/framework.

When system is built, no one wants to baby sit after its up and running. Therefore, there is a strong desire to automate everything, including error handling. But sometimes automation is not suitable for every error, and here is a good example.

I’m new to Windows Azure, and learning by making mistakes. There’s a lot to learn about Azure in general, and one of the interesting aspects is deployments and cost associated with it. Taking this moment, I’d like to thank Yves Goeleven, Azure MVP, who has helped me a lot.

When packaging Windows Azure solution from within Visual Studio .NET 2010, CSPACK is generating cspackproperties file behind the scenes, defaulting to .NET 3.5 Framework. I missed that part when going over the documentation and had to go through the worker role that can’t starts and no error is logged, since worker never loads. Gladly, solution is trivial and so old that is probably long time forgotten by the Azure veterans. But for newbies like myself, don’t dismiss old material, even if it’s from 2010.  Nothing New Under the Sky…

In the past I have always created on premises solutions for web applications that have mostly based on the server side code responsible for front UI and backend code, with a little to none client side code (usually called “scripting” with intention that it is not really a code), predominant validation on the server side with some duplication on the client. Technology of choice was ASP.NET MVC. When choice was not mine, sometime it would be ASP.NET WebForms. Services would be created using WCF, without auto-generated proxies.

Sometimes very basic things are so rooted in our heads that we often forget how to explain those basics to others. So was in my case when I needed to prove my son that A(B+C) is AB+AC and not just AB+C as he originally thought. To my surprise, I couldn’t think of a way to visualize it and explain. Wait a second, if you can’t explain something you supposedly know, then you don’t really know it well… Gladly, a friend of mine remind me the way to prove it. Why am I sharing this incident? Because a lot of times we assume we know something, till we actually need to explain it to others, and that’s where our knowledge is truly tested. This is something that is greatly exposed in pair-programming. And maybe that’s the reason so many avoid it with every possible excuse out there. Just saying…

I have ran into a problem when tried to pull down a project from subversion repository that uses self-signed certificate. This post has helped tremendously.

This exception drove me nuts: