Skip to main content

I did get forced, I got a software service that forced me to buy more licenses.

If you did visit Dreamforce 10 this year in moscone center, SFO, you have witness the Microsoft campaign about I didn't get forced. If you didn't, well, you were not at Dreamforce.

So the campaign from Microsoft was fine, but apart from catchy phrases and possibly the attempt to bank on Salesforce customers, the campaign was sheer lie. Now, I should add a disclaimer, I do not work for/ work with  Salesforce.com and also, they do not pay me to say this, but this is based on my experience.

I was a dedicated .Net developer (and still prefer that over Java any-day) and a few months ago I saw the announcement on Channel 9 about Azure.

I was excited, obviously, and registered for a CTP of the same. Now, I am a old timer with Windows and I have no intention of using jazzy animation, the thing girls at college used to shreak, (in fact, now I use windows only for Photoshop, rest all is ubuntu) so I was quite happy with windows xp and its slow yet stable operating system. Imagine my horror that to run azure, I had install IIS 7, which needed Vista or Windows 7.
When contacted, I received a reply that Microsoft won't be supporting XP anymore. What was more, they further mentioned that I need to pay for new Vista or windows 7 licenses. Now, thats not fair is it? Forcing users to buy more crap from you.

Aah, now you know, why I suddenly switched to ubuntu. As far as microsoft is concerned, here is my answer to them, in the classic angry birds style. paaathooooo.... aaah... (that is what is keeping me glued on my android)

So long then.
"Good bye, old friend. May the Force be with you."

Popular posts from this blog

The curious case of the custom redirection on Salesforce Console

Every developer worth their salt knows that the easiest way of redirection from a page to another is by using everyone's favorite function

public PageReference redirect() { PageReference pageRef = page.peskyProblemRedirection; pageRef.setRedirect(true); return pageRef; }
And the method is called by adding it to the Action attribute of the CommandButton or link, which works like charm and the user is redirected to the page after completion of the action.
So why am I going back to the basics? Because this way of redirection causes a pesky little problem in using the Service Cloud or Sales Cloud console.

Let's illustrate the problem, let's say you have a visualforce page as follows:

<apex:page sidebar="false" showHeader="false" controller="myExampleController"> <apex:form > <apex:pageBlock > <apex:pageBlockButtons > <apex:commandButton action="{!Redirect}&qu…

Some PDF tricks on Visualforce: Landscape, A4, page number and more

The beauty of Visualforce is simplicity. Remember the shock you received when you were told the entire page renders as PDF if you just add renderAs=PDF to the Page tag.

For those who thought I spoke alien language right now, here is the trick, to render a page as PDF, we add a simple attribute to the <apex: page> tag

<apex: page renderAs='pdf'> This will render the entire page as PDF.

Now, say we need to add some extra features to the PDF. Like a page number in the footer or we need to render the page in landscape mode. Faced with this problem, I put on my Indiana Jones hat and went hunting for it in the vast hay-sack of the internet (read: googled extensively). Imagine my happiness when i found a big big page with many big big examples to solve the problem. The document I am referring to is from W3C, paged Box media.

Long story short, I now possess the ultimate secret of rendering the page in any format I want. So here are few tricks I learned from the page. To p…

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…