So your plugin has a Custom View Engine which overrides _ProductAttributes.cshtml
And the custom theme plugin has a Custom View Engine which overrides _ProductAttributes.cshtml
It sounds like you need to make sure your Custom View Engine executes first. I don't have any experience with Custom View Engines, but there should be some way to do this.
And the custom theme plugin has a Custom View Engine which overrides _ProductAttributes.cshtml
It sounds like you need to make sure your Custom View Engine executes first. I don't have any experience with Custom View Engines, but there should be some way to do this.
No!!
That is not what I'm asking for. I'm overriding view page, let say _ProductAttributes.cshtml from plugin, also add some custom code to that override view. At the same time I'm using some theme which has same page inside.
Now, If I run the application, it will take my view page..as it's overriding existing theme's view page.
But in this case UI of _ProductAttributes.cshtml page will be different from them's design. So end user will have to change designing to make it compatible with theme.
I don't want to do this..so let's think about another case. If I not overriding view page from my plugin, then I'll not able to add my changes to view page (except using action filter, but injecting would not be convenient way to me).
But, I want to run override view page with theme compatibility.
Currently, end user have to manually add my custom code to the theme folder.
So, basically, I'm asking for solution to get rid out of it.
Hope you get it clear now!!