Using multiple models in tabs with Razor Pages Viewcomponent .Net Core 2.1












0















I have a slightly more complex requirement than your average single Viewcomponent that I'm trying to solve for.



I've built a web app with Razor Pages using .Net Core 2.1 and Entity Framework



On one of the pages I have a tabbed view that I use to input and display information in various formats, I've built each "tab" as an individual razor page for now as they all use multiple models, one to display and one to capture data.
I've tried using partial views without any luck as when I try change the tab the whole page reloads, not ideal and quite a bit slower.



Enter Viewcomponents, I can get a simple viewcomponent that consumes one model to work fine, but for the other tabs where I have 2-3 models injected/bound I cannot seem to find a way of implementing this.
Am I asking too much of the framework?



NB. I'm trying to do this using only razor pages with CSharp and no Javascript.
Is this even possible or should I throw in the towel and just move to Angular-MVC?






c# razor entity-framework-core asp.net-core-2.1 asp.net-core-viewcomponent







share|improve this question

























  • Razor renders on the server-side, which is why it "loads slower" for each page. Angular loads slower on initial load, so it depends on your use case. If you want a SPA-like behaviour, you'll definitely want to use JavaScript on top of Razor.

    – Brian
    Nov 13 '18 at 13:53













  • @Brian thanks for confirming, I was hoping to get away with it without incorporating JavaScript.

    – Kevin T
    Nov 13 '18 at 14:34
















0















I have a slightly more complex requirement than your average single Viewcomponent that I'm trying to solve for.



I've built a web app with Razor Pages using .Net Core 2.1 and Entity Framework



On one of the pages I have a tabbed view that I use to input and display information in various formats, I've built each "tab" as an individual razor page for now as they all use multiple models, one to display and one to capture data.
I've tried using partial views without any luck as when I try change the tab the whole page reloads, not ideal and quite a bit slower.



Enter Viewcomponents, I can get a simple viewcomponent that consumes one model to work fine, but for the other tabs where I have 2-3 models injected/bound I cannot seem to find a way of implementing this.
Am I asking too much of the framework?



NB. I'm trying to do this using only razor pages with CSharp and no Javascript.
Is this even possible or should I throw in the towel and just move to Angular-MVC?






c# razor entity-framework-core asp.net-core-2.1 asp.net-core-viewcomponent







share|improve this question

























  • Razor renders on the server-side, which is why it "loads slower" for each page. Angular loads slower on initial load, so it depends on your use case. If you want a SPA-like behaviour, you'll definitely want to use JavaScript on top of Razor.

    – Brian
    Nov 13 '18 at 13:53













  • @Brian thanks for confirming, I was hoping to get away with it without incorporating JavaScript.

    – Kevin T
    Nov 13 '18 at 14:34














0












0








0








I have a slightly more complex requirement than your average single Viewcomponent that I'm trying to solve for.



I've built a web app with Razor Pages using .Net Core 2.1 and Entity Framework



On one of the pages I have a tabbed view that I use to input and display information in various formats, I've built each "tab" as an individual razor page for now as they all use multiple models, one to display and one to capture data.
I've tried using partial views without any luck as when I try change the tab the whole page reloads, not ideal and quite a bit slower.



Enter Viewcomponents, I can get a simple viewcomponent that consumes one model to work fine, but for the other tabs where I have 2-3 models injected/bound I cannot seem to find a way of implementing this.
Am I asking too much of the framework?



NB. I'm trying to do this using only razor pages with CSharp and no Javascript.
Is this even possible or should I throw in the towel and just move to Angular-MVC?






c# razor entity-framework-core asp.net-core-2.1 asp.net-core-viewcomponent







share|improve this question
















I have a slightly more complex requirement than your average single Viewcomponent that I'm trying to solve for.



I've built a web app with Razor Pages using .Net Core 2.1 and Entity Framework



On one of the pages I have a tabbed view that I use to input and display information in various formats, I've built each "tab" as an individual razor page for now as they all use multiple models, one to display and one to capture data.
I've tried using partial views without any luck as when I try change the tab the whole page reloads, not ideal and quite a bit slower.



Enter Viewcomponents, I can get a simple viewcomponent that consumes one model to work fine, but for the other tabs where I have 2-3 models injected/bound I cannot seem to find a way of implementing this.
Am I asking too much of the framework?



NB. I'm trying to do this using only razor pages with CSharp and no Javascript.
Is this even possible or should I throw in the towel and just move to Angular-MVC?






c# razor entity-framework-core asp.net-core-2.1 asp.net-core-viewcomponent




c# razor entity-framework-core asp.net-core-2.1 asp.net-core-viewcomponent






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 13 '18 at 14:33







Kevin T

















asked Nov 13 '18 at 13:42









Kevin TKevin T

478




478













  • Razor renders on the server-side, which is why it "loads slower" for each page. Angular loads slower on initial load, so it depends on your use case. If you want a SPA-like behaviour, you'll definitely want to use JavaScript on top of Razor.

    – Brian
    Nov 13 '18 at 13:53













  • @Brian thanks for confirming, I was hoping to get away with it without incorporating JavaScript.

    – Kevin T
    Nov 13 '18 at 14:34



















  • Razor renders on the server-side, which is why it "loads slower" for each page. Angular loads slower on initial load, so it depends on your use case. If you want a SPA-like behaviour, you'll definitely want to use JavaScript on top of Razor.

    – Brian
    Nov 13 '18 at 13:53













  • @Brian thanks for confirming, I was hoping to get away with it without incorporating JavaScript.

    – Kevin T
    Nov 13 '18 at 14:34

















Razor renders on the server-side, which is why it "loads slower" for each page. Angular loads slower on initial load, so it depends on your use case. If you want a SPA-like behaviour, you'll definitely want to use JavaScript on top of Razor.

– Brian
Nov 13 '18 at 13:53







Razor renders on the server-side, which is why it "loads slower" for each page. Angular loads slower on initial load, so it depends on your use case. If you want a SPA-like behaviour, you'll definitely want to use JavaScript on top of Razor.

– Brian
Nov 13 '18 at 13:53















@Brian thanks for confirming, I was hoping to get away with it without incorporating JavaScript.

– Kevin T
Nov 13 '18 at 14:34





@Brian thanks for confirming, I was hoping to get away with it without incorporating JavaScript.

– Kevin T
Nov 13 '18 at 14:34












1 Answer
1






active

oldest

votes


















1














There's a few options available to you. Your best path forward, honestly, is a wrapper class, essentially a model of models, if you will. You simply create a class with properties on it for each of the individual models you actually need. This then allows you to use this as the model for your page, but still access all your individual models for the tabs.



View components are a valid approach, but there's two things you should realize:




  1. View component rendering is entirely self-contained. In other words, your main action/view turns into basically a stub, not really doing anything on its own. Instead, all the logic for building your model and passing it to the view for each tab is contained in the view component corresponding to that tab.


  2. View components are just about rendering HTML to a page. You cannot post to a view component. You'd still be posting to your actual main action, so that would need to be setup to handle whatever the tab in question is doing.



Finally, you're at least going to need JavaScript for your tab interface, if you don't want to roundtrip to the server each time you change tabs. Tab switching while staying put is dynamic functionality that is only possible with JavaScript.






share|improve this answer
























  • thanks, I've considered the wrapper class, but I'm using EF and the table models to display and edit data, I was just pondering the intricacies of going that route with modified state datamodels and if it was even possible without a mountain of manual updating on the server side. I already have all that logic sitting in the PageModels at the moment so including it in the viewcomponent will be easy enough. It's looking like Javascript would just be easier in this instance. Here I was hoping to prove a point without it.

    – Kevin T
    Nov 13 '18 at 14:41













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53282368%2fusing-multiple-models-in-tabs-with-razor-pages-viewcomponent-net-core-2-1%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














There's a few options available to you. Your best path forward, honestly, is a wrapper class, essentially a model of models, if you will. You simply create a class with properties on it for each of the individual models you actually need. This then allows you to use this as the model for your page, but still access all your individual models for the tabs.



View components are a valid approach, but there's two things you should realize:




  1. View component rendering is entirely self-contained. In other words, your main action/view turns into basically a stub, not really doing anything on its own. Instead, all the logic for building your model and passing it to the view for each tab is contained in the view component corresponding to that tab.


  2. View components are just about rendering HTML to a page. You cannot post to a view component. You'd still be posting to your actual main action, so that would need to be setup to handle whatever the tab in question is doing.



Finally, you're at least going to need JavaScript for your tab interface, if you don't want to roundtrip to the server each time you change tabs. Tab switching while staying put is dynamic functionality that is only possible with JavaScript.






share|improve this answer
























  • thanks, I've considered the wrapper class, but I'm using EF and the table models to display and edit data, I was just pondering the intricacies of going that route with modified state datamodels and if it was even possible without a mountain of manual updating on the server side. I already have all that logic sitting in the PageModels at the moment so including it in the viewcomponent will be easy enough. It's looking like Javascript would just be easier in this instance. Here I was hoping to prove a point without it.

    – Kevin T
    Nov 13 '18 at 14:41


















1














There's a few options available to you. Your best path forward, honestly, is a wrapper class, essentially a model of models, if you will. You simply create a class with properties on it for each of the individual models you actually need. This then allows you to use this as the model for your page, but still access all your individual models for the tabs.



View components are a valid approach, but there's two things you should realize:




  1. View component rendering is entirely self-contained. In other words, your main action/view turns into basically a stub, not really doing anything on its own. Instead, all the logic for building your model and passing it to the view for each tab is contained in the view component corresponding to that tab.


  2. View components are just about rendering HTML to a page. You cannot post to a view component. You'd still be posting to your actual main action, so that would need to be setup to handle whatever the tab in question is doing.



Finally, you're at least going to need JavaScript for your tab interface, if you don't want to roundtrip to the server each time you change tabs. Tab switching while staying put is dynamic functionality that is only possible with JavaScript.






share|improve this answer
























  • thanks, I've considered the wrapper class, but I'm using EF and the table models to display and edit data, I was just pondering the intricacies of going that route with modified state datamodels and if it was even possible without a mountain of manual updating on the server side. I already have all that logic sitting in the PageModels at the moment so including it in the viewcomponent will be easy enough. It's looking like Javascript would just be easier in this instance. Here I was hoping to prove a point without it.

    – Kevin T
    Nov 13 '18 at 14:41
















1












1








1







There's a few options available to you. Your best path forward, honestly, is a wrapper class, essentially a model of models, if you will. You simply create a class with properties on it for each of the individual models you actually need. This then allows you to use this as the model for your page, but still access all your individual models for the tabs.



View components are a valid approach, but there's two things you should realize:




  1. View component rendering is entirely self-contained. In other words, your main action/view turns into basically a stub, not really doing anything on its own. Instead, all the logic for building your model and passing it to the view for each tab is contained in the view component corresponding to that tab.


  2. View components are just about rendering HTML to a page. You cannot post to a view component. You'd still be posting to your actual main action, so that would need to be setup to handle whatever the tab in question is doing.



Finally, you're at least going to need JavaScript for your tab interface, if you don't want to roundtrip to the server each time you change tabs. Tab switching while staying put is dynamic functionality that is only possible with JavaScript.






share|improve this answer













There's a few options available to you. Your best path forward, honestly, is a wrapper class, essentially a model of models, if you will. You simply create a class with properties on it for each of the individual models you actually need. This then allows you to use this as the model for your page, but still access all your individual models for the tabs.



View components are a valid approach, but there's two things you should realize:




  1. View component rendering is entirely self-contained. In other words, your main action/view turns into basically a stub, not really doing anything on its own. Instead, all the logic for building your model and passing it to the view for each tab is contained in the view component corresponding to that tab.


  2. View components are just about rendering HTML to a page. You cannot post to a view component. You'd still be posting to your actual main action, so that would need to be setup to handle whatever the tab in question is doing.



Finally, you're at least going to need JavaScript for your tab interface, if you don't want to roundtrip to the server each time you change tabs. Tab switching while staying put is dynamic functionality that is only possible with JavaScript.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 13 '18 at 14:17









Chris PrattChris Pratt

152k20235299




152k20235299













  • thanks, I've considered the wrapper class, but I'm using EF and the table models to display and edit data, I was just pondering the intricacies of going that route with modified state datamodels and if it was even possible without a mountain of manual updating on the server side. I already have all that logic sitting in the PageModels at the moment so including it in the viewcomponent will be easy enough. It's looking like Javascript would just be easier in this instance. Here I was hoping to prove a point without it.

    – Kevin T
    Nov 13 '18 at 14:41





















  • thanks, I've considered the wrapper class, but I'm using EF and the table models to display and edit data, I was just pondering the intricacies of going that route with modified state datamodels and if it was even possible without a mountain of manual updating on the server side. I already have all that logic sitting in the PageModels at the moment so including it in the viewcomponent will be easy enough. It's looking like Javascript would just be easier in this instance. Here I was hoping to prove a point without it.

    – Kevin T
    Nov 13 '18 at 14:41



















thanks, I've considered the wrapper class, but I'm using EF and the table models to display and edit data, I was just pondering the intricacies of going that route with modified state datamodels and if it was even possible without a mountain of manual updating on the server side. I already have all that logic sitting in the PageModels at the moment so including it in the viewcomponent will be easy enough. It's looking like Javascript would just be easier in this instance. Here I was hoping to prove a point without it.

– Kevin T
Nov 13 '18 at 14:41







thanks, I've considered the wrapper class, but I'm using EF and the table models to display and edit data, I was just pondering the intricacies of going that route with modified state datamodels and if it was even possible without a mountain of manual updating on the server side. I already have all that logic sitting in the PageModels at the moment so including it in the viewcomponent will be easy enough. It's looking like Javascript would just be easier in this instance. Here I was hoping to prove a point without it.

– Kevin T
Nov 13 '18 at 14:41




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53282368%2fusing-multiple-models-in-tabs-with-razor-pages-viewcomponent-net-core-2-1%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Bressuire

Image
Subprefecture and commune in Nouvelle-Aquitaine, France Bressuire Subprefecture and commune Chateau de Bressuire and the Eglise Notre-Dame Coat of arms Location of Bressuire Bressuire Show map of France Bressuire Show map of Nouvelle-Aquitaine Coordinates: 46°50′27″N 0°29′14″W  /  46.8408°N 0.4872°W  / 46.8408; -0.4872 Coordinates: 46°50′27″N 0°29′14″W  /  46.8408°N 0.4872°W  / 46.8408; -0.4872 Country France Region Nouvelle-Aquitaine Department Deux-Sèvres Arrondissement Bressuire Canton Bressuire Government  • Mayor .mw-parser-output .nobold{font-weight:normal} (2014–20) Jean Michel Bernier Area 1 180.59 km 2 (69.73 sq mi) Population (2014) 2 19,300  • Density 110/km 2 (280/sq mi) Time zone UTC+01:00 (CET)  • Summer (DST) UTC+02:00 (CEST) INSEE/Postal code 79049 /79300 Elevation 98–236 m (322–774 ft) (avg. 173 m or 568 ft) 1 French Land Register data, which exclude...
Read more

Vorschmack

Image
Vorschmack Ukrainian Jewish-style vorschmack served on rye bread Course Hors d'oeuvre Region or state Eastern Europe Associated national cuisine Ashkenazi Jewish, Finnish, German, Ukrainian, Polish, Russian Main ingredients Ground meat and/or fish Cookbook: Vorschmack   Media: Vorschmack Vorschmack or forshmak (Yiddish: פֿאָרשמאַק ‎, from archaic German Vorschmack , "foretaste" [1] or "appetizer" [2] ) is an originally East European dish made of salty minced fish or meat. Different variants of this dish are especially common in Ashkenazi Jewish and Finnish cuisine. Some varieties are also known in Russian and Polish cuisine. Contents 1 In Jewish cuisine 2 In Russian cuisine 3 In Polish cuisine 4 In Finnish cuisine 5 See also 6 References In Jewish cuisine According to Gil Marks, the German name points to the possible Germanic origin of this dish. [1] William Pokhlyobkin descr...
Read more

Quarantine

Image
For other uses, see Quarantine (disambiguation). Signal flag "Lima" called the "Yellow Jack" which when flown in harbor means ship is under quarantine. A simple yellow flag (also called the "Yellow Jack") had historically been used to signal quarantine (it stands for Q among signal flags), but now indicates the opposite, as a signal of a ship free of disease that requests boarding and inspection. A quarantine is used to separate and restrict the movement of people; it is 'a restraint upon the activities or communication of persons or the transport of goods designed to prevent the spread of disease or pests', for a certain period of time. [1] This is often used in connection to disease and illness, such as those who may possibly have been exposed to a communicable disease. [2] The term is often erroneously used to mean medical isolation, which is "to separate ill persons who have a communicable disease from those who are healthy...
Read more