The governor limits are really quite pitiful: 16 level recursion, 1 meg heap, no more than 200 objects returned from a query, no more than 20 queries in one invocation. Salesforce has a very specific idea of what one would want to develop, and if your application isn't well within those boundaries, steer clear! Salesforce is a rather painful experience for developing anything but the most simple applications. Has anyone any experience of developing an application on salesforce as compared to the more 'traditional'. There doesn't seem to be much neutral sober analysis of the platform on the web that isn't salesforce's own material/blogs The Salesforce licensing model on the face of it suits this sort of flexibilty, but I'm worried about the development flexibilty/learning curve and all the issues that surround lock-in. Traditionally we have used our character based Works Mangement system for everything and tweaked it for each contract. The nature of the business is in the main 2-5 concurrent construction type contracts that run for 3-5 yrs each, each requiring 15-50 system users. net experience and my manager with a more legacy Synergy programming background, and I am self taught and am looking at evaluating other RAD options (eg Ironspeed).
However, there's only really myself with.
Net, and the obvious 1st choice would be asp.net. I've been trying it out with a view to recreating our own Works Management system on the platform. I have recently discovered that is much more than an online CRM after coming across a Morrison's Case Study in which they develop a works management application.
0 kommentar(er)
