Skip to main content
deleted 38 characters in body
Source Link
Adrian Larson
  • 151.3k
  • 38
  • 247
  • 431

You can wrap your component in a visualforce page, that you can then use within your classic interface, with close to the same code.

Look at Using Lightning Components in Visualforce pages

The only subtlety is that you have to handle either app event firing or just the e.force events in either experiences: Classic or Lightning in your code to make it generic and the same code base.

Hope this helps...

You can wrap your component in a visualforce page, that you can then use within your classic interface, with close to the same code.

Look at Using Lightning Components in Visualforce pages

The only subtlety is that you have to handle either app event firing or just the e.force events in either experiences: Classic or Lightning in your code to make it generic and the same code base.

Hope this helps...

You can wrap your component in a visualforce page, that you can then use within your classic interface, with close to the same code.

Look at Using Lightning Components in Visualforce pages

The only subtlety is that you have to handle either app event firing or just the e.force events in either experiences: Classic or Lightning in your code to make it generic and the same code base.

Source Link

You can wrap your component in a visualforce page, that you can then use within your classic interface, with close to the same code.

Look at Using Lightning Components in Visualforce pages

The only subtlety is that you have to handle either app event firing or just the e.force events in either experiences: Classic or Lightning in your code to make it generic and the same code base.

Hope this helps...