Skip to main content
7 events
when toggle format what by license comment
Oct 25, 2016 at 2:30 comment added Robert Sussland Yes, porting their app to lightning will take time. But their existing VF app will continue to work as well, it will be surfaced in a VF iframe.
Oct 24, 2016 at 15:51 comment added Mohith Shrivastava @RobertSussland The question mentions use of VF .Changing classes is fine but with auraenabled it will take some time for author to convert VF markups to lightning component and also rewire all logic via JS controllers
Oct 24, 2016 at 14:02 comment added Robert Sussland To add another comment, Salesforce is excellent about keeping your old app working. Even S-Control based apps still work today. You don't need to rewrite anything to keep existing functionality. But if you want to migrate from one technology to another, then that requires some porting to use the new technology. In this case, changing \@RemoteAction to \@AuraEnabled is not a big ideal. The work is on the client, creating lightning components.
Oct 24, 2016 at 13:59 comment added Garima Kour lol ... we require it urgently, so I wish there was a button like that .. :) Anyways, thanks for the details.
Oct 24, 2016 at 13:56 comment added Robert Sussland Yes, that's what it takes. Unfortunately you are talking about two different languages and porting work is required. This could be mitigated with some tooling to auto-rewrite sources, but there is no button that you can press to convert a lightning app into a visualforce app or vice versa.
Oct 24, 2016 at 13:54 comment added Garima Kour I have an existing fully developed application which is supporting Salesforce classic. I want to make it lightening compatible now but I get this error for almost all the pages because of the remoting methods. Separately creating AuraEnabled lightning methods will be altogether a new implementation
Oct 24, 2016 at 13:39 history answered Robert Sussland CC BY-SA 3.0