In your case, if the data will be persisted in a different database, that does not use the Sitefinity model, the best approach would be to go with a static module - be it an intrastate module(inheriting from ModuleBase
), or a Content-based one (inheriting from ContentModuleBase
), as this would give you more freedom when implementing the custom module provider with EF.
This brings us back to your initial question on achieving similar look and feel like the out of the box static modules. Please note that as Josh pointed out in his blog post
, the intra-site modules (inheriting from ModuleBase) are not using any Sitefinity components. On the onther hand, inheriting from ContentModuleBase would deliver the backend grids and frontend ContentView widgets functionality with it. For a more detailed example I'd recommend checking out the Products Catalog
sample from our Sitefinity SDK.
All the best,
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items