if you don't already, download the VS template for a nop 4.3 plugin development. This will give you the structure for plugin
https://github.com/nopSolutions/nopCommerce-plugin-template-VSI'm not experienced in theme development, but in nop the general flow for preparing a view is..
-Controller action calls service layer to get the Domain object(data)
-Controller action makes a call to Factory layer to prepare the view model, passing in the Domain object and returning a prepared model.
-Controller action returns the view, with prepared model.
So to follow nop patterns, you will need your own Service, Factory, in addition to your controllers/models/views.
Have a look at another plugin in the source code, for example Nop.Plugin.Shipping.FixedByWeightOrTotal
And also look at the front-end code in Nop.Web.Controllers to see how preparing the views hangs together
gatisc wrote:Thank You for quick response! No I don't need to store data in data base. I need to develop a plugin for my new child theme, which can pass another model, not ProductOverviewModel but my xxxxxxProductOverviewModel, where xxxxxx name of my child theme. I need to use This new model's fields like manufacturer. Name in _ProductBox.