Saturday, August 28, 2010

Comic - Engineering Process

Disclaimer: The intent of this comic strip is pure fun. No harm is intended to anyone.

Artist: Alone Dreamer




Copyright: Do not hotlink to the above images and Do not replicate the graphics without the prior permission of the author.

Comic - Triage Bug Bar

Artist: Alone Dreamer

Triage bar goes high as a product reaches closer to the General Availability.

Friday, August 27, 2010

Comic - A Feature Team Meeting in Company

Disclaimer – No offense is meant to anyone living or dead Smile

A typical feature team meeting in a Software Company (Name withdrawn upon request).

Duet Taskflow Feature Team Meeting

Click the image above for the full version of the image

Credit: Alone Dreamer

Saturday, August 21, 2010

Some VS Bugs


"the page has one or more <asp:content> that do not correspond with <asp:ContentPlaceHolder> controls in masterpage"

Apparently I’m using a wrong contentPlaceHolderId which doesn’t exist in my master page but that’s not true. Here is my Page

<asp:Content ContentPlaceHolderID="Head" runat="server">
<asp:Content ContentPlaceHolderID="Content" runat="server">

And my Master page looks like this

<head id="h" runat="server">    
<title id="t" runat="server" title='<%$ CurrentPage: Title %>' />
<asp:ContentPlaceHolder ID="Head" runat="server">
<link rel="canonical" href="<%= CurrentPage != null ? CurrentPage.Url : Request.RawUrl %>" />


It all looks good to me so where is the problem? Error message is not very friendly in this case and error and solution both seems pretty weird.
Solution: The title tag should not be used as a single closed tag e.g. <title /> instead it should be written as <title></title> and the problem will go away. Look out for other tags as well such as <script />. It doesn’t work very well in the single close tag. Use explicit close tag wherever possible. Browsers are forgiving in nature but not the VS

Thursday, August 19, 2010

Solution: Facebook Social Plugins not working in IE

What to do when you’ve worked hard to integrate Facebook plugins with your website and they look cool on Firefox/Chrome but all of a sudden you feel disappointed when it doesn’t work at all in IE, or may be works sometime but not always (as in my case).

Being an avid IE fan and user, I can’t just sit back and relax when it’s not working on IE. So here is a small modification you need to make to your page when you feel you’ve done everything correct but your fb:like or fb:login-button are still not working.
Add the xmlns:fb namespace to your page and you are done. I just forgot to add this to my page and was living in frustration for one whole day until I came across this post. Then I realized it was a silly mistake and I should’ve added this before when my Visual Studio was complaining about the unrecognized fb tag Smile

<html xmlns:fb="">

I hope it helps some people implementing Facebook connect on their pages.

Sunday, August 15, 2010

Bowling at its worst :)

This is us playing bowling at Extreme Sports Bar Hyderabad.

Let’s see how we play :)

This is Suneet playing his second best lol..

Now you know how was his first best :) People moved their children away after his ball hit the pins Why?? ‘coz it hit the pins in the another lane… Lol

I was not behind though.. this is how I like to play


Google Analytics

Popular Posts

Powered by Blogger.