Skip to main content
replaced http://salesforce.stackexchange.com/ with https://salesforce.stackexchange.com/
Source Link

Following the description here to make an Lightning Component available in Visualforcehere to make an Lightning Component available in Visualforce, I found, that the Lightning App does no longer work as expected as a Standalone App via

/c/appName.app

The js code and the callouts seem to be happen, but the screen stays just empty. The reason is the presence of

extends="ltng:outApp"

Is that behavior intended this way, so that an app can only be used either Standalone OR extending ltng:outApp and never both at the same time?

Following the description here to make an Lightning Component available in Visualforce, I found, that the Lightning App does no longer work as expected as a Standalone App via

/c/appName.app

The js code and the callouts seem to be happen, but the screen stays just empty. The reason is the presence of

extends="ltng:outApp"

Is that behavior intended this way, so that an app can only be used either Standalone OR extending ltng:outApp and never both at the same time?

Following the description here to make an Lightning Component available in Visualforce, I found, that the Lightning App does no longer work as expected as a Standalone App via

/c/appName.app

The js code and the callouts seem to be happen, but the screen stays just empty. The reason is the presence of

extends="ltng:outApp"

Is that behavior intended this way, so that an app can only be used either Standalone OR extending ltng:outApp and never both at the same time?

Source Link
Uwe Heim
  • 28.5k
  • 20
  • 121
  • 287

Does <aura:application ... extends="ltng:outApp" /> stop the usability via /c/appName.app?

Following the description here to make an Lightning Component available in Visualforce, I found, that the Lightning App does no longer work as expected as a Standalone App via

/c/appName.app

The js code and the callouts seem to be happen, but the screen stays just empty. The reason is the presence of

extends="ltng:outApp"

Is that behavior intended this way, so that an app can only be used either Standalone OR extending ltng:outApp and never both at the same time?