I agree with TheTXI...like a lot of ASP.NET technologies, you aren't really going to get much benefit from Web Parts unless you buy into the model 100%.
But aside from that, we had some technical issues as well, mainly related to cross-browser UI rendering problems. These might have been fixed in recent releases, I don't know: we ended up rolling our own solution.
ASP.NET MVC 越来越受到关注。 它实际上是把其他一切都从水中吹出来。 我建议先调查一下。 Sharepoint 可能很快就会合并 MVC。
ASP.NET MVC is getting so much traction. It is literally blow everything else out of the water. I would recommend look into that first. Sharepoint probably will incorporate MVC very soon.
Support for user editable properties and personalization built in
Customizable Editor Parts
Customizable standard WebPart menus
Drag'n'Drop WebParts between WebPartZones
Support for connections between WebParts, useful for master/detail views, filters, and more
Can load UserControls
Disadvantages:
Higher Resource Usage
Visual Studio currently does not have designer support for WebParts
Like ocdecio mentioned, ASP.NET MVC would probably be a better choice nowadays, at least outside of the SharePoint world, where WebParts are very important.
EDIT:
For an overview of ASP.NET 2.0 WebParts, you may want to look at:
I personally wouldn't recommend WebParts for your application unless you are going to go full-blown into the webparts portal paradigm. I played around with them sparingly and it just doesn't feel like it would be as effective as designing your own pieces.
根据我的经验，Web 部件对于为 SharePoint 创建内容非常有用。 但现在有了 ASP.NET MVC，我不确定它们是否是标准 ASP.NET 应用程序的不错选择。
In my experience web parts are useful to create content for SharePoint. But now with ASP.NET MVC I'm not sure they will be a good choice for a standard ASP.NET application.
发布评论
评论（5）
我同意 TheTXI 的观点...就像许多 ASP.NET 技术一样，除非您 100% 相信该模型，否则您不会真正从 Web 部件中获得太多好处。
但除此之外，我们还遇到了一些技术问题，主要与跨浏览器 UI 渲染问题有关。 这些可能已在最近的版本中得到修复，我不知道：我们最终推出了自己的解决方案。
I agree with TheTXI...like a lot of ASP.NET technologies, you aren't really going to get much benefit from Web Parts unless you buy into the model 100%.
But aside from that, we had some technical issues as well, mainly related to cross-browser UI rendering problems. These might have been fixed in recent releases, I don't know: we ended up rolling our own solution.
ASP.NET MVC 越来越受到关注。 它实际上是把其他一切都从水中吹出来。 我建议先调查一下。 Sharepoint 可能很快就会合并 MVC。
ASP.NET MVC is getting so much traction. It is literally blow everything else out of the water. I would recommend look into that first. Sharepoint probably will incorporate MVC very soon.
WebPart 相对于 UserControls 的优点：
缺点：
就像 ocdecio 提到的那样，ASP.NET MVC 现在可能是更好的选择，至少在 SharePoint 世界之外（WebPart 在 SharePoint 世界中非常重要）。
编辑：
有关 ASP.NET 2.0 WebParts 的概述，您可能需要查看：
在 ASP.Net 2.0 中使用 WebPart 和
通过以下方式个性化您的门户用户控件和自定义 Web 部件
Advantages of WebParts over UserControls:
Disadvantages:
Like ocdecio mentioned, ASP.NET MVC would probably be a better choice nowadays, at least outside of the SharePoint world, where WebParts are very important.
EDIT:
For an overview of ASP.NET 2.0 WebParts, you may want to look at:
Using WebParts in ASP.Net 2.0 and
Personalize Your Portal with User Controls and Custom Web Parts
我个人不会推荐您的应用程序使用 WebParts，除非您要全面了解 WebParts 门户范例。 我很少尝试使用它们，但感觉它不如自己设计作品那么有效。
I personally wouldn't recommend WebParts for your application unless you are going to go full-blown into the webparts portal paradigm. I played around with them sparingly and it just doesn't feel like it would be as effective as designing your own pieces.
根据我的经验，Web 部件对于为 SharePoint 创建内容非常有用。 但现在有了 ASP.NET MVC，我不确定它们是否是标准 ASP.NET 应用程序的不错选择。
In my experience web parts are useful to create content for SharePoint. But now with ASP.NET MVC I'm not sure they will be a good choice for a standard ASP.NET application.