{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 爷、活的狠高调 的问题《What is the point of Partial Views in Asp.net MVC》','https://www.manongdao.com/q-290132.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Ive noticed that there seems to be no real difference between a view and a partial view. For instance, one can create a view but can render it as a partial view by using
@Html.Partial("ViewName")
or by specifying that its action return it as
return PartialView();
Ive noticed that the opposite is also the case - ie, one can create a partial view but if it is returned as a full view, it will be displayed with the default layout for the views.
My question is this - When adding a new view in Visual Studio, one is given the option of creating a view that is partial or not. Isn't this redundant, since a view can be rendered as both a partial and a full view anyway?
Practically , there is no difference among them. But when you acknowledge an html object as Partial View then, it is considered as a self-contained object which may get serve at different places just like a web-part/User-Controls and also its lightweight.
Partial view kept to use as partial page of the main page(parent page).
What does mean of partial view? Actually in the main page we will have all the HTML page attributes as below:
html lang="en"
head
title
meta
body
But in partial view we will not have all above attributes.
Find the features of partial page:
1. Partial page will be light wait and get fitted into the any view.
2. This will use as the reusable component.
3. Partial view will be render inside of a View(parent view or page).
For all who coming from ASP.Net background they can understand partial view as user control.
Thanks Afazal mdafazal@gmail.com
Think of partial views as user controls in ASP.NET WebForms. Partial views are used if you want to have a functionality centralized, so it can be used in many parts of your website. This is the purpose of partial views.
Hope I have answered your question.
Two things. First, to an extent you are right. But it's more of a semantic thing to seperate reusable code. It also comes in handy when for e.g. say you need to display a dialog but only when the user has some sort of an interaction with the page, like the click of a button. With partial views you don't have to have the markup for this on the page when it loads thereby reducing the file size. When you write markup/code in the partial view, you don't have to do the whole
<html></html>code block. Instead you just create a<div></div>or whatever you need.The bit about creating a view in Visual Studio. No, it's not redundant because when you create a partial view, it does not use your master layout file.
There is difference between views and partial views, and the difference is more about their usage, rather than technical.
View is meant to be used as full page of your application, it needs layout,
<html>and<title>. Partial views are more like reusable parts of other views. Partials do not represent full pages, they are inserted into other views.From technical point of view,
return View("SameView");renders view including layout page, and returning that same view byreturn PartialView("SameView");renders contents, but omits contents of layout page.No difference - it's true. But when you say "Partial View" all your teammates understand that you mean reusable views that will be used in many places across the website.