Hii..
I am using a Multiview for a application. Each aspx page contains Multiview.
A single multiview contains atleast 5 to 6 views. (so less no. of aspx pages). When user clicks any button such as say "Edit View" (where user can edit his entries), a diffrent view is displayed. So user feels that he is redirected to another page. So a single aspx page has lot of controls, lot of code - a lil bit heavy page.
Will it affect loading time? is it better to use different aspx pages?
It is better to use different pages for different views. The number of aspx pages doesn't affect the performance, but managing each view on its own page is easier for maintenance.
You may use Multiview for some sort of wizard, but it is better to not use it to just reduce the number of aspx pages in the app.
Alex is right. Even if your views aren't displayed the controls contained in those views are persisted in the __VIEWSTATE. if you take a look at the source of your pages in your browser theres proably going to be a few Kb's of VIEWSTATE.
A colleague once built a page that had 380Kb of VIEWSTATE. That will affect performance!
Multiviews can work great in minimalist settings, but don't do like I did early on and attempt to build the equivalent to a 15 page medical form all in one ASPX page using the MultiView. If you are building short and sweet panes your performance will not suffer as much, but you will eventually cross the threshold and your performance will go into the gutter.
Related
I am trying to build an Admin page that already uses the same Master the rest of my site does. Within this Admin page, I have a sidebar with links for different things that an Admin user needs to do. I want those links to load HTML/Razor content in the center of the page but I want to not make separate Admin pages for each bit of functionality.
What strategy or process would work best for this situation? Every search result I'm finding seems to be just learning about how to make a simple Master, but I don't want to make multiple Masters for my site.
(I'm very new to all this, but I learn fast from examples and references.)
There are many ways to solve this problem from dynamically change the UI by fetching from server through Ajax calls to Simple tabs.
As you said you are new to this you can use tabs
As development of an ASP.NET Web Forms project rolls on, the code used in markup sometimes becomes repetitive.
Are master pages my only option to reuse that markup? Sometimes my Master page content won't refresh. Maybe it's time to replace it with something similar if it exists.
Yes, use a UserControl but that would be wired alternative cause in that case you will have to create separate usercontrol for header/footer/menu item ... etc and have them registered on each page separately using a #Register page directive.
I've been working on a project and I noticed I reuse the same menu over and over again and it got to a point where, if I needed to change something I would need to change 20+ pages too because of it being a menu.
My question is, is it possible to have a single aspx file with the working menu on it, and have the other pages call it? So far I've tried
<?php include('Menu.aspx') ?>
<iframe id="myIframe" src="Menu.aspx" height="100%" width="100%"></iframe>
The later (iframe) showed something but I was unable to resize it and the links didn't work either. The php one didn't show anything. Any help would be appreciated, thank you very much.
You can use the following approaches to solve this:
Master Pages allow to have a common layout that is applied to several aspx pages. The master page defines a layout and provides some content placeholders that are filled in by the pages that reference the master page. Your example of a menu fits good; the menu would be placed on the master page. See this link for details.
Another way to share layouts are ASP.NET UserControls. These are created as ascx files and can be reused in several aspx pages. See this link for details.
The best option for you is to create an User Control, and use it in all your pages.
An user control is similar to a server control (e.g. asp textbox, update panel etc.), but custom made by the developer to suit his specific needs.
If the menu is more like the common layout/theme of all your pages you can use a Master Page instead.
You have to make yourself familiar with master pages. See this as a beginner tutorial: http://www.codeproject.com/Articles/333650/Beginner-s-Tutorial-on-Master-Pages-in-ASP-NET
There are two option to reuse menu in asp.net page.
Master Page
User Control
using sitemap and add into master page.
https://msdn.microsoft.com/en-us/library/aa581781.aspx
http://webproject.scottgu.com/CSharp/MasterPages/MasterPages.aspx
Hope this will help you.
thanks
I am creating a web application C# asp.net . I have a simple menu but I do no know if using
iframes to show different options according to the menu is better than using a masterpage.
I am pretty new at this. I read that iframes are not being used anymore.
Is there any other option that I can use?
Thanks
Yeah, I wouldn't use iframes in that context. At one point they were used to give the impression of something akin to Ajax, but you'll really only find them used these days for embedding videos, audio, etc. from other sites (e.g. YouTube, Soundcloud). Master pages should suffice - you'll have a master page with the menu itself, and any menu selection will load an entirely different page, albeit with the same menu provided by the master page. If you're looking to provide navigation without an entire page refresh, then you're getting into the realm of SPAs (single page applications), which will require the use of Ajax.
I have an ASP.NET web application that I am making and I am thinking of making it a tabbed interface using Telerik's RadTabStrip. I am trying to figure out the best way to approach this though. I would need about 10 tabs because I have about 10 different main areas of my application. My question is how is the best way to integrate the content into the tabs. All of the simple examples I've seen create RadViews with imbedded HTML/ASP.NET content. The problem with this approach is that, with 10 tabs, it would make my main ASPX file really really big and it would be kind of clumsy to work with, having to integrate all 10 pages into one page. Is there a better or more accepted way to accomplish this?
I think, you have several possibilities:
Use one RadTabStrip and several RadView controls. Put the content for each tab into a separate user control (*.ascx). Then you only have to include the user controls in your main aspx page.
Use a master page and put the RadTabStrip on it. Create a separate page for each area of your application (each using the same master page). Use the RadTab's NavigateUrl property to navigate to the corresponding page (as shown in this demo).
there are certainly other possibilities...