Comments on: Microsoft Azure: Building Custom Extensions vs. Altering the Architecture http://www.crmoutsiders.com/2009/07/14/microsoft-azure-building-custom-extensions-vs-altering-the-architecture/?utm_source=rss&utm_medium=rss&utm_campaign=microsoft-azure-building-custom-extensions-vs-altering-the-architecture Former analyst and journalist discuss CRM from the vendor-side Thu, 09 Feb 2012 18:49:59 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: aoymdbvtp http://www.crmoutsiders.com/2009/07/14/microsoft-azure-building-custom-extensions-vs-altering-the-architecture/comment-page-1/#comment-4716 aoymdbvtp Thu, 22 Sep 2011 16:44:16 +0000 http://www.crmoutsiders.com/?p=857#comment-4716 RB3w5l <a href="http://rjtobmxqelpu.com/" rel="nofollow">rjtobmxqelpu</a> RB3w5l rjtobmxqelpu

]]> By: Martin Schneider http://www.crmoutsiders.com/2009/07/14/microsoft-azure-building-custom-extensions-vs-altering-the-architecture/comment-page-1/#comment-1657 Martin Schneider Tue, 14 Jul 2009 18:14:04 +0000 http://www.crmoutsiders.com/?p=857#comment-1657 Colin - I agree in part with some of your points here, especially around how it is far easier to create an extension network that is upgradable rather than allow whole hog access to code. But to your points around Azure vs. Apex/Force - they are VERY similar even in marketing collateral. I remember as an analyst seeing a very similar slide from SFDC as to the one pictured in your post. Just replace .Net with Apex and they are virtually the same thing. Colin – I agree in part with some of your points here, especially around how it is far easier to create an extension network that is upgradable rather than allow whole hog access to code.

But to your points around Azure vs. Apex/Force – they are VERY similar even in marketing collateral. I remember as an analyst seeing a very similar slide from SFDC as to the one pictured in your post. Just replace .Net with Apex and they are virtually the same thing.

]]>